From: Pratyush Yadav <pratyush@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add test_kho to KHO's entry
Date: Thu, 20 Nov 2025 10:25:34 +0100 [thread overview]
Message-ID: <mafs0ms4h2gz5.fsf@kernel.org> (raw)
In-Reply-To: <2025111944-bullpen-slinging-dcdc@gregkh> (Greg KH's message of "Wed, 19 Nov 2025 17:02:49 +0100")
On Wed, Nov 19 2025, Greg KH wrote:
> On Wed, Nov 19, 2025 at 04:55:06PM +0100, Pratyush Yadav wrote:
>> On Wed, Nov 19 2025, Greg KH wrote:
>>
>> > On Tue, Nov 18, 2025 at 07:24:15PM +0100, Pratyush Yadav wrote:
>> >> Commit b753522bed0b7 ("kho: add test for kexec handover") introduced the
>> >> KHO test but missed adding it to KHO's MAINTAINERS entry. Add it so the
>> >> KHO maintainers can get patches for its test.
>> >>
>> >> Cc: stable@vger.kernel.org
>> >
>> > Why is this a patch for stable trees?
>>
>> If someone finds a problem with this test in a stable kernel, they will
>> know who to contact.
>
> Contacting developers/maintainers should always be done on the latest
> kernel release, not on older stable kernels as fixes need to ALWAYS be
> done on Linus's tree first.
>
> Please don't force us to attempt to keep MAINTAINERS changes in sync in
> stable kernel trees, that way lies madness and even more patches that
> you would be forcing me to handle :)
Okay, my bad. Feel free to ignore this patch then. And I will keep that
in mind the next time around.
Andrew, can you please drop the "Cc: stable@vger.kernel.org" when you
apply?
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2025-11-20 9:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 18:24 Pratyush Yadav
2025-11-18 18:35 ` Pasha Tatashin
2025-11-19 7:14 ` Mike Rapoport
2025-11-19 7:36 ` Greg KH
2025-11-19 15:55 ` Pratyush Yadav
2025-11-19 16:02 ` Greg KH
2025-11-20 9:25 ` Pratyush Yadav [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=mafs0ms4h2gz5.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=stable@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