All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>
Subject: Re: Patch "s390: select ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP" has been added to the 6.1-stable tree
Date: Mon, 23 Feb 2026 15:52:55 +0100	[thread overview]
Message-ID: <20260223155255.41342222@thinkpad-T15> (raw)
In-Reply-To: <20260222235114.1339059-1-sashal@kernel.org>

On Sun, 22 Feb 2026 18:51:14 -0500
Sasha Levin <sashal@kernel.org> wrote:

> This is a note to let you know that I've just added the patch titled
> 
>     s390: select ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP
> 
> to the 6.1-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      s390-select-arch_want_hugetlb_page_optimize_vmemmap.patch
> and it can be found in the queue-6.1 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.

Please don't add this to any stable tree. This feature is broken on s390,
and it recently was removed upstream via commit 64e2f60f355e ("s390:
Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP"), which also had a Cc: stable
and Fixes: 00a34d5a99c0.

So we'd rather want commit 64e2f60f355e added to stable v6.2+, than
adding the original commit 00a34d5a99c0 to older trees.

Thanks,
Gerald

       reply	other threads:[~2026-02-23 14:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260222235114.1339059-1-sashal@kernel.org>
2026-02-23 14:52 ` Gerald Schaefer [this message]
2026-02-23 19:22   ` Patch "s390: select ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP" has been added to the 6.1-stable tree Sasha Levin

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=20260223155255.41342222@thinkpad-T15 \
    --to=gerald.schaefer@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=sashal@kernel.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=svens@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.