[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260112115452.3e0f63ef@gandalf.local.home>
Date: Mon, 12 Jan 2026 11:54:52 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Masami Hiramatsu
<mhiramat@...nel.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Peter Zijlstra <peterz@...radead.org>, Josh Poimboeuf
<jpoimboe@...nel.org>, Jason Baron <jbaron@...mai.com>, Ard Biesheuvel
<ardb@...nel.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, rust-for-linux@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add Rust files to STATIC BRANCH/CALL and
TRACING
On Mon, 12 Jan 2026 16:11:40 +0100
Miguel Ojeda <miguel.ojeda.sandonis@...il.com> wrote:
> There are several ways subsystems have gone about it:
>
> - Sometimes they may just add the people to the existing entry.
>
> - Sometimes they create sub-entries like you suggest (usually with
> square brackets like " [RUST]" but there is also a " - RUST" used),
> e.g.
>
> BLOCK LAYER DEVICE DRIVER API [RUST]
> MEMORY MANAGEMENT - RUST
>
> - Sometimes they add them into the existing entry but with an added
> "(RUST)" after their names, e.g. Boqun in LOCKING PRIMITIVES:
>
> M: Boqun Feng <boqun.feng@...il.com> (LOCKDEP & RUST)
OK, add "[RUST]" instead ;-)
-- Steve
Powered by blists - more mailing lists