From: Miguel Ojeda <ojeda@kernel.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Boqun Feng" <boqun@kernel.org>, "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
Subject: [PATCH] MAINTAINERS: add `.rustfmt.toml` to "RUST" entry
Date: Mon, 23 Mar 2026 03:42:06 +0100 [thread overview]
Message-ID: <20260323024206.129401-1-ojeda@kernel.org> (raw)
`.rustfmt.toml` is not covered by `MAINTAINERS`, so tools like
`scripts/get_maintainer.pl` do not report it properly, e.g.:
$ scripts/get_maintainer.pl -f .rustfmt.toml
linux-kernel@vger.kernel.org (open list)
It should have been there since the beginning, and while it is not a big
deal since the file has not changed at all since it was added in commit
80db40bac8f4 ("rust: add `.rustfmt.toml`") back in 2022, this will be
especially useful to catch unintended unstable features if upstream
`rustfmt` started to allow them in stable toolchains [1][2].
Thus add it.
Link: https://github.com/rust-lang/rustfmt/issues/6829#issuecomment-4084325200 [1]
Link: https://github.com/rust-lang/rustfmt/issues/4884 [2]
Fixes: 80db40bac8f4 ("rust: add `.rustfmt.toml`")
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 77fdfcb55f06..a62f6af55c3a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -23146,6 +23146,7 @@ C: zulip://rust-for-linux.zulipchat.com
P: https://rust-for-linux.com/contributing
T: git https://github.com/Rust-for-Linux/linux.git rust-next
F: .clippy.toml
+F: .rustfmt.toml
F: Documentation/rust/
F: include/trace/events/rust_sample.h
F: rust/
base-commit: bf074eb6891be799174ff42e0051492681fdc045
--
2.53.0
next reply other threads:[~2026-03-23 2:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 2:42 Miguel Ojeda [this message]
2026-03-27 11:20 ` [PATCH] MAINTAINERS: add `.rustfmt.toml` to "RUST" entry 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=20260323024206.129401-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=lossin@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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