# Meeting 2024-06-12
<!-- Leave your topic starting with ### in the relevant sections below -->

## Critical
<!-- bugs, soundness issues, urgent patches/reviews etc. -->

## Status Reports
<!-- You want to report on something you are working on/request reviews.
Or you want to know the status of something someone else is doing -->

### Rust block layer API to be staged for merge :confetti_ball: :rocket:
* Jens will stage the patches for 6.11
* The first patches to be merged enable a simple driver that completes all requests
* More patches to follow in future releases as dependencies are upstreamed

### Kangrejos conference 2024
* Kangrejos will be in Copenhagen before LPC in September
* The dates are not final, but are expected to be two days in the period September 5 to September 13.

### Some interesting CI tooling from LSF

Patchwork with [KPD](https://github.com/facebookincubator/kernel-patches-daemon)

## Discussion Questions
<!-- Anything that requires lengthy discussion/more general questions also fit here -->

### XArray status and path forward
Andreas talked to Matthew Willcox about XArray at LSF. Matthew maintains that he cannot review the patches and ACK them due to lack of Rust knowledge. He does not have anyone in his network that can review the patches. He promised to try to take a look again, but he would still probably not be able to ACK anything without proper understanding.

Let's discuss potential paths forward.

### `undocumented_unsafe_blocks`
Now that we removed the `alloc` code, we might be able to turn on the `undocumented_unsafe_blocks` [clippy lint](https://rust-lang.github.io/rust-clippy/master/index.html#/undocumented_unsafe_blocks).

### `rustfmt`

* Fill columnt 80 or 100 chars? - our tools is set up for 80.
* Formatting of examples in doc comments?

Gary: max_width is 100, comment_width is 80 but it's not effective unless wrap_comments is enabled, which is a nightly-only feature.

Andreas: what's the rule for formatting comments then?

Miguel: no rule for now.

Gary: Enforce specific re-flowing rule will cause large diffs.

Perhaps have a rough guideline and allow people to re-flow as they prefer?

### 0-day kernel test robot

Miguel asked the 0-day kernel test robot about Andreas' message. They will add `rustfmtcheck`, check the doctests and they will enable the config options needed for the networking Rust code we have in the kernel.

## Miscellaneous
<!-- stuff that does not fit into other categories -->

### build_assert may be broken?

### Is `Device` Send?