linux-kernel - Re: [PATCH] MAINTAINERS: add Rust files to STATIC BRANCH/CALL and TRACING

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aWUO59edshSRit-Y@google.com>
Date: Mon, 12 Jan 2026 15:10:31 +0000
From: Alice Ryhl <aliceryhl@...gle.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@...il.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 10:00:06AM -0500, Steven Rostedt wrote:
> On Sun, 11 Jan 2026 19:36:29 +0100
> Miguel Ojeda <miguel.ojeda.sandonis@...il.com> wrote:
> 
> > On Wed, Jan 7, 2026 at 1:32 PM Alice Ryhl <aliceryhl@...gle.com> wrote:
> > >
> > > I'm proposing to include them under the existing entries, as that seems
> > > like the most obvious place to include them. However, there are multiple
> > > ways to do this. If you prefer to have them elsewhere, I would also be
> > > happy to create a new entry with me as maintaining them, or I'm also
> > > willing to be listed as R: under the entry. Regardless of how we list
> > > them in MAINTAINERS, I will be around if anything comes up. Let me know
> > > what you all prefer.  
> > 
> > I think this was meant to go after the `---`?
> > 
> > Whatever Steven et al. are happy with, this looks fine, thanks!
> > 
> > Acked-by: Miguel Ojeda <ojeda@...nel.org>
> > 
> 
> I guess the question is are those with expertise on the list of people to
> Cc?

I would be on cc either way as RUST includes F: rust/.

> 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?

Sure, we can do that.

Are you still willing to pick up the patches? I think that is simpler in
case there are any series that touch both the C and Rust parts. (Such as
the initial tracepoint series did.)

Alice