From: Miguel Ojeda <ojeda@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: [PATCH 0/3] Clean `rustfmt` formatting and define imports style
Date: Fri, 10 Oct 2025 19:43:48 +0200 [thread overview]
Message-ID: <20251010174351.948650-1-ojeda@kernel.org> (raw)
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
next reply other threads:[~2025-10-10 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 17:43 Miguel Ojeda [this message]
2025-10-10 17:43 ` [PATCH 1/3] docs: rust: add section on imports formatting Miguel Ojeda
2025-10-10 17:43 ` [PATCH 2/3] rust: alloc: employ a trailing comment to keep vertical layout Miguel Ojeda
2025-10-10 17:43 ` [PATCH 3/3] rust: cpufreq: fix formatting Miguel Ojeda
2025-10-13 4:48 ` Viresh Kumar
2025-10-10 20:31 ` [PATCH 0/3] Clean `rustfmt` formatting and define imports style Benno Lossin
2025-10-16 23:25 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251010174351.948650-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=torvalds@linux-foundation.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.