From: Chris Down <chris@chrisdown.name>
To: linux-kernel@vger.kernel.org
Cc: Petr Mladek <pmladek@suse.com>, kernel-team@fb.com
Subject: [PATCH] MAINTAINERS: Add printk indexing maintainers on mention of printk_index
Date: Wed, 30 Mar 2022 15:32:20 +0100 [thread overview]
Message-ID: <YkRp9IhToTmTnkl7@chrisdown.name> (raw)
This will primarily catch new and changed printk_index_subsys_emit
calls, but it's also worth catching changes to other printk indexing
infrastructure outside of kernel/printk/index.c.
This avoids churn due to missing ccs when adding new printk indexes, as
was the case recently for the first round of the XFS printk indexing
patches.
Signed-off-by: Chris Down <chris@chrisdown.name>
Cc: Petr Mladek <pmladek@suse.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e3b11033e628..45121b9e943d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -15404,6 +15404,7 @@ PRINTK INDEXING
R: Chris Down <chris@chrisdown.name>
S: Maintained
F: kernel/printk/index.c
+K: printk_index
PROC FILESYSTEM
L: linux-kernel@vger.kernel.org
--
2.35.1
next reply other threads:[~2022-03-30 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:32 Chris Down [this message]
2022-04-01 12:31 ` [PATCH] MAINTAINERS: Add printk indexing maintainers on mention of printk_index Petr Mladek
2022-04-01 12:32 ` Chris Down
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=YkRp9IhToTmTnkl7@chrisdown.name \
--to=chris@chrisdown.name \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
/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