linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: 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: Wed, 19 Nov 2025 17:02:49 +0100	[thread overview]
Message-ID: <2025111944-bullpen-slinging-dcdc@gregkh> (raw)
In-Reply-To: <mafs0wm3m2f1h.fsf@kernel.org>

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

thanks,

greg k-h


  reply	other threads:[~2025-11-19 16:02 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 [this message]
2025-11-20  9:25       ` Pratyush Yadav

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=2025111944-bullpen-slinging-dcdc@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=graf@amazon.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=pratyush@kernel.org \
    --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