From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
David Hildenbrand <david@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
oliver.sang@intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: avoid use of BIT() macro for initialising VMA flags
Date: Sat, 6 Dec 2025 16:35:30 +0000 [thread overview]
Message-ID: <492bf977-d590-47fc-bcba-898bbee01c16@lucifer.local> (raw)
In-Reply-To: <20251205191255.e6da75c8511d23159f44b59f@linux-foundation.org>
On Fri, Dec 05, 2025 at 07:12:55PM -0800, Andrew Morton wrote:
> On Sat, 6 Dec 2025 11:40:34 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi Andrew,
> >
> > On Fri, 5 Dec 2025 12:15:01 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> > >
> > > I'm not really sure what's the best way to determine this. I use
> > >
> > > hp2:/usr/src/mm> git tag --contains 2b6a3f061f11
> > > mm-everything-2025-11-29-19-43
> > > mm-everything-2025-12-01-19-02
> > > mm-everything-2025-12-03-23-49
> > > mm-everything-2025-12-05-00-55
> > > mm-stable-2025-12-03-21-26
> > >
> >
> > What does "git branch --contains 2b6a3f061f11" say in your tree?
>
> hp2:/usr/src/mm> git branch --contains 2b6a3f061f11
> * linus
> mm-everything
> mm-new
> mm-stable
> mm-unstable
> hp2:/usr/src/mm> git branch -r --contains 2b6a3f061f11
> linus/master
> origin/mm-everything
> origin/mm-new
> origin/mm-stable
> origin/mm-unstable
>
> kinda random, but it tells me "that's in mm-stable", which is what counts.
>
> > In my linux-next tree it says (I need the -r to check remote branches):
> >
> > $ git branch -r --contains 2b6a3f061f11
> > mm-stable/mm-stable
> > mm-unstable/mm-unstable
> >
> > but I don't export my remotes to my published tree.
Thanks guys for confirming, this is therefore less work all round :)
Though Andrew do please add the Fixes tag that I foolishly forgot to
include, thanks!
Cheers, Lorenzo
next prev parent reply other threads:[~2025-12-06 16:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 17:50 Lorenzo Stoakes
2025-12-05 17:52 ` Lorenzo Stoakes
2025-12-05 18:43 ` David Laight
2025-12-05 19:18 ` Lorenzo Stoakes
2025-12-05 21:34 ` David Laight
2025-12-06 16:43 ` Lorenzo Stoakes
2025-12-08 16:42 ` Lorenzo Stoakes
2025-12-08 18:57 ` David Laight
2025-12-09 8:28 ` Vlastimil Babka
2025-12-09 9:26 ` Mateusz Guzik
2025-12-10 16:18 ` Lorenzo Stoakes
2025-12-10 22:44 ` Mateusz Guzik
2025-12-12 12:24 ` Mateusz Guzik
2025-12-12 13:02 ` David Laight
2025-12-12 13:13 ` Mateusz Guzik
2025-12-12 15:03 ` Lorenzo Stoakes
2025-12-12 17:26 ` Mateusz Guzik
2025-12-05 21:49 ` David Laight
2025-12-06 16:47 ` Lorenzo Stoakes
2025-12-05 19:56 ` John Hubbard
2025-12-06 16:42 ` Lorenzo Stoakes
2025-12-05 20:15 ` Andrew Morton
2025-12-05 20:18 ` David Hildenbrand (Red Hat)
2025-12-06 0:40 ` Stephen Rothwell
2025-12-06 3:12 ` Andrew Morton
2025-12-06 16:35 ` Lorenzo Stoakes [this message]
2025-12-06 1:14 ` Al Viro
2025-12-06 1:26 ` Al Viro
2025-12-06 12:35 ` Vlastimil Babka
2025-12-06 16:34 ` Lorenzo Stoakes
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=492bf977-d590-47fc-bcba-898bbee01c16@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=oliver.sang@intel.com \
--cc=rppt@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=surenb@google.com \
--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
all inboxes | Powered by JetHome®