From: Alice Ryhl <aliceryhl@google.com>
To: Steven Rostedt <rostedt@goodmis.org>,
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>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org,
Alice Ryhl <aliceryhl@google.com>
Subject: [PATCH] MAINTAINERS: add Rust files to STATIC BRANCH/CALL and TRACING
Date: Wed, 07 Jan 2026 12:22:50 +0000 [thread overview]
Message-ID: <20260107-jump-label-rust-maintainers-v1-1-702b03482f2e@google.com> (raw)
I realized that these files were never listed in MAINTAINERS when they
were added in commit ad37bcd965fd ("rust: add tracepoint support").
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.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Based on v6.19-rc1.
I noticed it due to this patch:
https://patch.msgid.link/20260105-define-rust-helper-v2-9-51da5f454a67@google.com
---
MAINTAINERS | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5b11839cba9de1e9e43f63787578edd8c429ca39..14eafd3fb428483cfd3f0a86f52d0c62ba7436e5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -25017,6 +25017,9 @@ F: include/linux/jump_label*.h
F: include/linux/static_call*.h
F: kernel/jump_label.c
F: kernel/static_call*.c
+F: rust/helpers/jump_label.c
+F: rust/kernel/generated_arch_static_branch_asm.rs.S
+F: rust/kernel/jump_label.rs
STI AUDIO (ASoC) DRIVERS
M: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
@@ -26470,6 +26473,7 @@ F: include/linux/trace*.h
F: include/trace/
F: kernel/trace/
F: kernel/tracepoint.c
+F: rust/kernel/tracepoint.rs
F: scripts/tracing/
F: scripts/tracepoint-update.c
F: tools/testing/selftests/ftrace/
---
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
change-id: 20260107-jump-label-rust-maintainers-17040992e7db
Best regards,
--
Alice Ryhl <aliceryhl@google.com>
next reply other threads:[~2026-01-07 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 12:22 Alice Ryhl [this message]
2026-01-11 18:36 ` Miguel Ojeda
2026-01-12 15:00 ` Steven Rostedt
2026-01-12 15:10 ` Alice Ryhl
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=20260107-jump-label-rust-maintainers-v1-1-702b03482f2e@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®