From: Andrew Morton <akpm@linux-foundation.org>
To: "David Hildenbrand (Red Hat)" <david@kernel.org>
Cc: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Sourabh Jain <sourabhjain@linux.ibm.com>,
Borislav Petkov <bp@alien8.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Heiko Carstens <hca@linux.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, x86@kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6] mm/hugetlb: ignore hugepage kernel args if hugepages are unsupported
Date: Sun, 21 Dec 2025 10:49:07 -0800 [thread overview]
Message-ID: <20251221104907.032abf56c67f3e50c9c94e31@linux-foundation.org> (raw)
In-Reply-To: <655cc605-2ce1-4ccb-8cc0-a0a31a9c89fd@kernel.org>
On Sun, 21 Dec 2025 10:22:44 +0100 "David Hildenbrand (Red Hat)" <david@kernel.org> wrote:
> >
> > My main concern was -
> > A fixes tag means it might get auto backported to stable kernels too,
>
> Not in the MM world -- IIRC. I think there is the agreement, that we
> decide what should go into stable and what not.
>
> Andrew can correct me if my memory is wrong.
Yes, -stable maintainers have been asked to only backport patches where
the MM developers asked for that, with cc:stable. There may be
slipups, but as far as I know this is working.
I don't actually know how they determine which patches need this
special treatment. Pathname? Signed-off-by:akpm?
> But we can always jump in and say that something should not go to stable
> trees.
Yes, please jump in if there are any thoughts about
ordering/priority/timing. In fact, please jump in if there are any
thoughts at all ;)
next prev parent reply other threads:[~2025-12-21 18:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 5:36 Sourabh Jain
2025-12-21 5:59 ` Ritesh Harjani
2025-12-21 9:22 ` David Hildenbrand (Red Hat)
2025-12-21 18:49 ` Andrew Morton [this message]
2025-12-23 1:30 ` SeongJae Park
2025-12-23 2:30 ` Andrew Morton
2025-12-23 11:43 ` Sasha Levin
2025-12-23 16:54 ` Andrew Morton
2025-12-23 17:11 ` Sasha Levin
2025-12-22 3:12 ` Ritesh Harjani
2025-12-22 5:57 ` Sourabh Jain
2025-12-22 10:28 ` David Hildenbrand (Red Hat)
2025-12-22 10:54 ` Christophe Leroy (CS GROUP)
2025-12-23 5:48 ` Sourabh Jain
2025-12-22 5:39 ` Sourabh Jain
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=20251221104907.032abf56c67f3e50c9c94e31@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=christophe.leroy@csgroup.eu \
--cc=david@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=ritesh.list@gmail.com \
--cc=sourabhjain@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@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