From: Andrew Morton <akpm@linux-foundation.org>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Usama Arif <usama.arif@linux.dev>,
Pedro Falcato <pfalcato@suse.de>,
stable@vger.kernel.org, jannh@google.com, liam@infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
vbabka@kernel.org, chrisl@kernel.org, kasong@tencent.com,
baoquan.he@linux.dev, youngjun.park@lge.com, hannes@cmpxchg.org,
riel@surriel.com, shakeel.butt@linux.dev, kas@kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH] mm/mincore: handle non-swap entries before !CONFIG_SWAP guard
Date: Wed, 3 Jun 2026 11:23:41 -0700 [thread overview]
Message-ID: <20260603112341.1d1355a1e1e3a656665a9192@linux-foundation.org> (raw)
In-Reply-To: <aiAYt2pNBVAIBaFg@lucifer>
On Wed, 3 Jun 2026 13:07:04 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
> > >> Fixes: 1f2052755c15 ("mm/mincore: use a helper for checking the swap cache")
> > >> Signed-off-by: Usama Arif <usama.arif@linux.dev>
> > >
> > > LGTM, thanks!
> > >
> > > Reviewed-by: Pedro Falcato <pfalcato@suse.de>
> > >
> > > Maybe Cc: stable@kernel.org ?
> > >
> >
> > Ah yes, I have cc-ed stable in the reply to this email, but probably that
> > is not enough?
>
> Yeah I think a Cc: in the body is required,
It's required for MM patches because we've asked the -stable
maintainers to not auto-pick everything which has a Fixes:.
> but then again Andrew does add Cc's
> for Cc'd parties so maybe it'll be automagically sorted out.
cc:stable management is all manual here.
> Andrew - probably we're good here but just checking to be sure?
Yep, I'd added it thanks. But please always do check!
next prev parent reply other threads:[~2026-06-03 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 17:22 Usama Arif
2026-06-02 17:51 ` Pedro Falcato
2026-06-03 9:52 ` Usama Arif
2026-06-03 12:07 ` Lorenzo Stoakes
2026-06-03 18:23 ` Andrew Morton [this message]
2026-06-03 2:55 ` Kairui Song
2026-06-03 12:08 ` Lorenzo Stoakes
2026-06-03 12:20 ` Usama Arif
2026-06-03 15:02 ` Johannes Weiner
2026-06-08 15:34 ` Nhat Pham
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=20260603112341.1d1355a1e1e3a656665a9192@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=pfalcato@suse.de \
--cc=riel@surriel.com \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=youngjun.park@lge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®