Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Christoph Lameter (Ampere)" <cl@gentwo.org>
Cc: vbabka@suse.cz, harry.yoo@oracle.com, roman.gushchin@linux.dev,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] mm, slab: restore NUMA policy support for large kmalloc" failed to apply to 6.1-stable tree
Date: Mon, 18 Aug 2025 17:58:45 +0200	[thread overview]
Message-ID: <2025081809-taekwondo-blimp-2d91@gregkh> (raw)
In-Reply-To: <f423079b-6994-a2aa-8bcf-248f39e739b7@gentwo.org>

On Mon, Aug 18, 2025 at 08:07:30AM -0700, Christoph Lameter (Ampere) wrote:
> The breakage was introduced in 6.1 So maybe the fix is not needed?

If it is broken in 6.1, then yes, it needs to be fixed in 6.1.y :)

thanks,

greg k-h

      reply	other threads:[~2025-08-18 15:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 11:07 FAILED: patch "[PATCH] mm, slab: restore NUMA policy support for large kmalloc" failed to apply to 6.1-stable tree gregkh
2025-08-18 15:07 ` Christoph Lameter (Ampere)
2025-08-18 15:58   ` Greg KH [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=2025081809-taekwondo-blimp-2d91@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cl@gentwo.org \
    --cc=harry.yoo@oracle.com \
    --cc=roman.gushchin@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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