Skip to contentSkip to conversation

Clean `rustfmt` formatting and define imports style

PATCH Applied Miguel Ojeda 4 participants 7 messages Oct 10, 2025 – Oct 16, 2025

Subsystems (4)
lore
Share & tools
lore

Miguel Ojeda

author maintainer
#0 lore raw

cover Clean `rustfmt` formatting and define imports style

Hi Linus,

Please see these commits, especially the documentation one. It is a follow-up of the discussion on rustfmt.

If you are OK with it, please pick them up for -rc1 -- this should make CIs green and let people work easily after -rc1, which would help even if we decide to do something differently later on.

I can send a quick PR if you prefer.

Thanks!

Miguel Ojeda (3):
docs: rust: add section on imports formatting
rust: alloc: employ a trailing comment to keep vertical layout
rust: cpufreq: fix formatting

 Documentation/rust/coding-guidelines.rst | 75 ++++++++++++++++++++++++
 rust/kernel/alloc/kvec.rs                |  2 +-
 rust/kernel/cpufreq.rs                   |  3 +-
 3 files changed, 77 insertions(+), 3 deletions(-)

--
2.51.0

author maintainer
#1 lore raw

PATCH 1/3 docs: rust: add section on imports formatting

rustfmt, by default, formats imports in a way that is prone to conflicts while merging and rebasing, since in some cases it condenses several items into the same line.

For instance, Linus mentioned [1] that the following case:

    use crate::{
        fmt,
        page::AsPageIter,
    };

is compressed by rustfmt into:

    use crate::{fmt, page::AsPageIter};

which is undesirable.

Similarly, rustfmt may put several items in the same line even if the braces span already multiple lines, e.g.:

    use kernel::{
        acpi, c_str,
        device::{property, Core},
        of, platform,
    };

The options that control the formatting behavior around imports are generally unstable, and rustfmt releases do not allow to use nightly features, unlike the compiler and other Rust tooling [2].

For the moment, we can introduce a workaround to prevent rustfmt from compressing the example above -- the "trailing empty comment":

    use crate::{
        fmt,
        page::AsPageIter, //
    };

which is reminiscent of the trailing comma behavior in other formatters. We already used empty comments for formatting purposes in the past, e.g. in commit b9b701fce49a ("rust: clarify the language unstable features in use").

In addition, rustfmt actually reformats with a vertical layout (i.e. it does not put two items in the same line) when seeing such a comment, i.e. it doesn't just preserve the formatting, which is good in the sense that we can use it to easily reformat some imports, since it matches the style we generally want to have.

A Git merge driver would help (suggested by Gary and Wedson), though maintainers would need to set it up, the diffs would still be larger and the formatting rules for imports would remain hard to predict.

Thus document the style that we will follow in the coding guidelines by introducing a new section and explain how the trailing empty comment works there too.

We discussed the issue with upstream Rust in our usual Rust <-> Rust for Linux meeting [3], and there have also been a few other discussions in parallel in issues [4][5] and Zulip [6]. We will see what happens, but upstream Rust has already created a subteam of rustfmt to try to overcome the bandwidth issue [7], which is a good signal, and some organization work has already started (e.g. tracking issues). We will continue our discussions with them about it.

---
 Documentation/rust/coding-guidelines.rst | 75 ++++++++++++++++++++++++
 1 file changed, 75 insertions(+)
Documentation/rust/coding-guidelines.rst +75 -0
index 6ff9e754755d..3198be3a6d63 100644
@@ -38,6 +38,81 @@ Like ``clang-format`` for the rest of the kernel, ``rustfmt`` works on
 individual files, and does not require a kernel configuration. Sometimes it may
 even work with broken code.
 
+Imports
+~~~~~~~
+
+``rustfmt``, by default, formats imports in a way that is prone to conflicts
+while merging and rebasing, since in some cases it condenses several items into
+the same line. For instance:
+
+.. code-block:: rust
+
+	// Do not use this style.
+	use crate::{
+	    example1,
+	    example2::{example3, example4, example5},
+	    example6, example7,
+	    example8::example9,
+	};
+
+Instead, the kernel uses a vertical layout that looks like this:
+
+.. code-block:: rust
+
+	use crate::{
+	    example1,
+	    example2::{
+	        example3,
+	        example4,
+	        example5, //
+	    },
+	    example6,
+	    example7,
+	    example8::example9, //
+	};
+
+That is, each item goes into its own line, and braces are used as soon as there
+is more than one item in a list.
+
+The trailing empty comment allows to preserve this formatting. Not only that,
+``rustfmt`` will actually reformat imports vertically when the empty comment is
+added. That is, it is possible to easily reformat the original example into the
+expected style by running ``rustfmt`` on an input like:
+
+.. code-block:: rust
+
+	// Do not use this style.
+	use crate::{
+	    example1,
+	    example2::{example3, example4, example5, //
+	    },
+	    example6, example7,
+	    example8::example9, //
+	};
+
+The trailing empty comment works for nested imports, as shown above, as well as
+for single item imports -- this can be useful to minimize diffs within patch
+series:
+
+.. code-block:: rust
+
+	use crate::{
+	    example1, //
+	};
+
+The trailing empty comment works in any of the lines within the braces, but it
+is preferred to keep it in the last item, since it is reminiscent of the
+trailing comma in other formatters. Sometimes it may be simpler to avoid moving
+the comment several times within a patch series due to changes in the list.
+
+There may be cases where exceptions may need to be made, i.e. none of this is
+a hard rule. There is also code that is not migrated to this style yet, but
+please do not introduce code in other styles.
+
+Eventually, the goal is to get ``rustfmt`` to support this formatting style (or
+a similar one) automatically in a stable release without requiring the trailing
+empty comment. Thus, at some point, the goal is to remove those comments.
+
 
 Comments
 --------
Signature · 1 line
2.51.0
author maintainer
#2 lore raw

PATCH 2/3 rust: alloc: employ a trailing comment to keep vertical layout

In reply to Miguel Ojeda

Apply the formatting guidelines introduced in the previous commit to make the file rustfmt-clean again.

---
 rust/kernel/alloc/kvec.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
rust/kernel/alloc/kvec.rs +1 -1
index e94aebd084c8..ac8d6f763ae8 100644
@@ -9,7 +9,7 @@
 };
 use crate::{
     fmt,
-    page::AsPageIter,
+    page::AsPageIter, //
 };
 use core::{
     borrow::{Borrow, BorrowMut},
Signature · 1 line
2.51.0
author maintainer
#3 lore raw

PATCH 3/3 rust: cpufreq: fix formatting

In reply to Miguel Ojeda

We do our best to keep the repository rustfmt-clean, thus run the tool to fix the formatting issue.

Fixes f97aef092e19 ("cpufreq: Make drivers using CPUFREQ_ETERNAL specify transition latency")
---
 rust/kernel/cpufreq.rs | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
rust/kernel/cpufreq.rs +1 -2
index 21b5b9b8acc1..1a555fcb120a 100644
@@ -38,8 +38,7 @@
 const CPUFREQ_NAME_LEN: usize = bindings::CPUFREQ_NAME_LEN as usize;
 
 /// Default transition latency value in nanoseconds.
-pub const DEFAULT_TRANSITION_LATENCY_NS: u32 =
-        bindings::CPUFREQ_DEFAULT_TRANSITION_LATENCY_NS;
+pub const DEFAULT_TRANSITION_LATENCY_NS: u32 = bindings::CPUFREQ_DEFAULT_TRANSITION_LATENCY_NS;
 
 /// CPU frequency driver flags.
 pub mod flags {
Signature · 1 line
2.51.0
maintainer Acked-by on v1 3/3
#4 lore raw

Re: [PATCH 3/3] rust: cpufreq: fix formatting

Quoted 16 lines · Miguel Ojeda

We do our best to keep the repository rustfmt-clean, thus run the tool to fix the formatting issue.

Fixes f97aef092e19 ("cpufreq: Make drivers using CPUFREQ_ETERNAL specify transition latency")
---
 rust/kernel/cpufreq.rs | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
rust/kernel/cpufreq.rs +0 -0
index 21b5b9b8acc1..1a555fcb120a 100644

rust/kernel/cpufreq.rs line 44

Quoted 9 lines
rust/kernel/cpufreq.rs +1 -2
@@ -38,8 +38,7 @@
 const CPUFREQ_NAME_LEN: usize = bindings::CPUFREQ_NAME_LEN as usize;
 
 /// Default transition latency value in nanoseconds.
-pub const DEFAULT_TRANSITION_LATENCY_NS: u32 =
-        bindings::CPUFREQ_DEFAULT_TRANSITION_LATENCY_NS;
+pub const DEFAULT_TRANSITION_LATENCY_NS: u32 = bindings::CPUFREQ_DEFAULT_TRANSITION_LATENCY_NS;
 
 /// CPU frequency driver flags.
 pub mod flags {
Signature · 1 line
viresh
reviewer Reviewed-by on the v1 series
#5 lore raw
In reply to Miguel Ojeda
Quoted 18 lines · Miguel Ojeda

Hi Linus,

Please see these commits, especially the documentation one. It is a follow-up of the discussion on rustfmt.

If you are OK with it, please pick them up for -rc1 -- this should make CIs green and let people work easily after -rc1, which would help even if we decide to do something differently later on.

I can send a quick PR if you prefer.

Thanks!

Miguel Ojeda (3):
docs: rust: add section on imports formatting
rust: alloc: employ a trailing comment to keep vertical layout
rust: cpufreq: fix formatting

Quoted 4 lines
 Documentation/rust/coding-guidelines.rst | 75 ++++++++++++++++++++++++
 rust/kernel/alloc/kvec.rs                |  2 +-
 rust/kernel/cpufreq.rs                   |  3 +-
 3 files changed, 77 insertions(+), 3 deletions(-)

For the series:

---
Cheers,
Benno

Applied
#6 lore raw
In reply to Miguel Ojeda
Quoted 6 lines · Miguel Ojeda

Hi Linus,

Please see these commits, especially the documentation one. It is a follow-up of the discussion on rustfmt.

Quoted 7 lines

If you are OK with it, please pick them up for -rc1 -- this should make CIs green and let people work easily after -rc1, which would help even if we decide to do something differently later on.

I can send a quick PR if you prefer.

Thanks!

Since I didn't hear anything, I will send you the PR after tomorrow's linux-next.

Applied to rust-fixes (plus one I just sent to the list) -- thanks everyone!

Cheers,
Miguel