rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Rust 'rustfmt'
Date: Sat, 18 Oct 2025 20:28:00 +0200	[thread overview]
Message-ID: <20251018182800.1592965-1-ojeda@kernel.org> (raw)

Hi Linus,

This is the PR for:

    https://lore.kernel.org/rust-for-linux/20251010174351.948650-1-ojeda@kernel.org/

It has only been a day in linux-next, but it is trivial. I based this
on a non-tag because there was one more change merged this week.

No conflicts expected. No functional changes intended.

Please pull -- thanks!

Cheers,
Miguel

The following changes since commit 98ac9cc4b4452ed7e714eddc8c90ac4ae5da1a09:

  Merge tag 'f2fs-fix-6.18-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs (2025-10-16 10:58:49 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux.git tags/rust-rustfmt

for you to fetch changes up to 1f1d3e1d094db732d22b892227bf1e1ac3a8ca04:

  rust: bitmap: fix formatting (2025-10-17 13:02:22 +0200)

----------------------------------------------------------------
Rust 'rustfmt' cleanup

'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.

Document in our guidelines that we will handle this for the moment with
the trailing empty comment workaround and make the tree 'rustfmt'-clean
again.

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

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

             reply	other threads:[~2025-10-18 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 18:28 Miguel Ojeda [this message]
2025-10-18 20:07 ` [GIT PULL] Rust 'rustfmt' pr-tracker-bot

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=20251018182800.1592965-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=rust-for-linux@vger.kernel.org \
    --cc=tmgross@umich.edu \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).