From: Alice Ryhl <aliceryhl@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jason Baron <jbaron@akamai.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add Rust files to STATIC BRANCH/CALL and TRACING
Date: Mon, 12 Jan 2026 15:10:31 +0000 [thread overview]
Message-ID: <aWUO59edshSRit-Y@google.com> (raw)
In-Reply-To: <20260112100006.7db6d31d@gandalf.local.home>
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@gmail.com> wrote:
>
> > On Wed, Jan 7, 2026 at 1:32 PM Alice Ryhl <aliceryhl@google.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@kernel.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
next prev parent reply other threads:[~2026-01-12 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 12:22 [PATCH] MAINTAINERS: add Rust files to STATIC BRANCH/CALL and TRACING Alice Ryhl
2026-01-11 18:36 ` Miguel Ojeda
2026-01-12 15:00 ` Steven Rostedt
2026-01-12 15:10 ` Alice Ryhl [this message]
2026-01-12 16:54 ` Steven Rostedt
2026-01-26 12:27 ` Alice Ryhl
2026-01-26 21:37 ` Peter Zijlstra
2026-01-26 21:58 ` Alice Ryhl
2026-01-27 8:24 ` Peter Zijlstra
2026-01-27 8:26 ` Alice Ryhl
2026-01-12 15:11 ` Miguel Ojeda
2026-01-12 16:54 ` Steven Rostedt
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=aWUO59edshSRit-Y@google.com \
--to=aliceryhl@google.com \
--cc=ardb@kernel.org \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.