[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nY2xUj0aG4q7YOKxt0EV29Jwos_kjAPD89eE3_irsr0g@mail.gmail.com>
Date: Mon, 12 Jan 2026 16:11:40 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>
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, Jan 12, 2026 at 4:00 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> I guess the question is are those with expertise on the list of people to
> Cc?
>
> I think it may be better to have a separate section for RUST so that the
> rust maintainers can be included in the M: part too. Perhaps:
>
> STATIC BRANCH/CALL (RUST)
>
> and
>
> TRACING (RUST)
>
> And have the M of the other sections be R here?
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)
Cheers,
Miguel
Powered by blists - more mailing lists