From: Chris Down <chris@chrisdown.name>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] MAINTAINERS: Add printk indexing maintainers on mention of printk_index
Date: Fri, 1 Apr 2022 13:32:51 +0100 [thread overview]
Message-ID: <Ykbw82LY7fvJD/mI@chrisdown.name> (raw)
In-Reply-To: <YkbuovatudROyl4b@alley>
Petr Mladek writes:
>On Wed 2022-03-30 15:32:20, Chris Down wrote:
>> 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>
>
>Nice trick. I was not aware of that K: entries.
>
>I have pushed the patch into printk/linux.git, branch for-5.19.
>
>We missed the direct 5.18 train. I will add the commit into
>a printk pull request for 5.18-rcX if there is any. But I think
>that it is not worth creating a pull request just with this change.
>
>I am going to make sure that you are added into CC in the meantime.
>I hope that they will add me at least ;-)
Sounds good, thank you! :-)
prev parent reply other threads:[~2022-04-01 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 14:32 [PATCH] MAINTAINERS: Add printk indexing maintainers on mention of printk_index Chris Down
2022-04-01 12:31 ` Petr Mladek
2022-04-01 12:32 ` Chris Down [this message]
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=Ykbw82LY7fvJD/mI@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