From: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
To: peterz@infradead.org
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jslaby@suse.cz>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jason Baron <jbaron@akamai.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH] MAINTAINERS: add static_call_inline.c to STATIC BRANCH/CALL
Date: Wed, 2 Nov 2022 09:41:34 +0100 [thread overview]
Message-ID: <20221102084134.4094-1-jirislaby@kernel.org> (raw)
From: Jiri Slaby <jslaby@suse.cz>
Commit 8fd4ddda2f49 (static_call: Don't make __static_call_return0
static) split static_call.c and static_call_inline.c was created. This
was not reflected in MAINTAINERS.
Fix it now by adding a static_call*.c glob.
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Jason Baron <jbaron@akamai.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 379945f82a64..401b170a168d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19634,7 +19634,7 @@ F: arch/*/kernel/static_call.c
F: include/linux/jump_label*.h
F: include/linux/static_call*.h
F: kernel/jump_label.c
-F: kernel/static_call.c
+F: kernel/static_call*.c
STI AUDIO (ASoC) DRIVERS
M: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
--
2.38.1
next reply other threads:[~2022-11-02 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 8:41 Jiri Slaby (SUSE) [this message]
2022-11-02 21:05 ` [PATCH] MAINTAINERS: add static_call_inline.c to STATIC BRANCH/CALL Josh Poimboeuf
-- strict thread matches above, loose matches on Subject: below --
2025-01-09 11:47 [PATCH] MAINTAINERS: Add " Jiri Slaby (SUSE)
2022-09-21 9:17 [PATCH] MAINTAINERS: add " Jiri Slaby
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=20221102084134.4094-1-jirislaby@kernel.org \
--to=jirislaby@kernel.org \
--cc=ardb@kernel.org \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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