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: <aXddnjiHCX-XS5S9@google.com>
Date: Mon, 26 Jan 2026 12:27:10 +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 11:54:08AM -0500, Steven Rostedt wrote:
> On Mon, 12 Jan 2026 15:10:31 +0000
> Alice Ryhl <aliceryhl@...gle.com> wrote:
> 
> > > 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.)
> 
> Yes. So I guess you can still add me with a 'M:'. But I wanted a separate
> section so that all the Rust expertise is still included.

What about the STATIC BRANCH/CALL subsystem? Should I also leave you or
someone else as 'M:' there? It's unclear to me who usually picks up
patches for STATIC BRANCH/CALL when they are not a dependency to a patch
for somewhere else.

Alice