Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 1 Apr 2022 13:32:51 +0100
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
Message-ID: <Ykbw82LY7fvJD/mI@chrisdown.name>
References: <YkRp9IhToTmTnkl7@chrisdown.name>
 <YkbuovatudROyl4b@alley>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <YkbuovatudROyl4b@alley>
User-Agent: Mutt/2.2.2 (aa28abe8) (2022-03-25)
Precedence: bulk

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! :-)