From: Mike Rapoport <rppt@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Usama Arif <usama.arif@linux.dev>,
david@kernel.org, chrisl@kernel.org, kasong@tencent.com,
ziy@nvidia.com, linux-mm@kvack.org, ying.huang@linux.alibaba.com,
Baoquan He <baoquan.he@linux.dev>,
willy@infradead.org, youngjun.park@lge.com, hannes@cmpxchg.org,
riel@surriel.com, shakeel.butt@linux.dev, alex@ghiti.fr,
kas@kernel.org, baohua@kernel.org, dev.jain@arm.com,
baolin.wang@linux.alibaba.com, npache@redhat.com,
"Liam R. Howlett" <liam@infradead.org>,
ryan.roberts@arm.com, Vlastimil Babka <vbabka@kernel.org>,
lance.yang@linux.dev, linux-kernel@vger.kernel.org,
nphamcs@gmail.com, shikemeng@huaweicloud.com,
kernel-team@meta.com
Subject: Re: [PATCH 0/6] mm: preparatory patches for PMD level swap entries
Date: Thu, 2 Jul 2026 16:08:03 +0300 [thread overview]
Message-ID: <akZis7j6xSjl8K_D@kernel.org> (raw)
In-Reply-To: <akY_L-yuaCXBOXb3@lucifer>
On Thu, Jul 02, 2026 at 11:48:24AM +0100, Lorenzo Stoakes wrote:
> +cc Mike re: CI.
>
> On Wed, Jul 01, 2026 at 04:46:13PM -0700, Andrew Morton wrote:
> > On Wed, 1 Jul 2026 09:04:33 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
> >
> > > On Tue, Jun 30, 2026 at 12:50:24PM -0700, Andrew Morton wrote:
> > > > On Tue, 30 Jun 2026 09:34:37 -0700 Usama Arif <usama.arif@linux.dev> wrote:
> > > >
> > > > > This is the preparatory part of the PMD page table swapin work.
> > > >
> > > > Thanks.
> > > >
> > > > This comes reasonably reviewed, so I'll queue it in mm-new.
> > > >
> > > > Why?
> > > >
> > > > - Human review coverage and AI review make me believe this isn't the
> > > > final version at all, but I do believe this is something we want in
> > > > 7.2, and getting it under test early will help to push it along.
> > > >
> > > > - Getting it in there early means that others will base their work on
> > > > material which will probably be upstreamed this cycle, so this gives
> > > > them a more accurate base against which to work.
> > > >
> > > > Sashiko did find a lot to talk about, some of it pre-existing so can
> > > > people who work on this code please take a look at
> > > >
> > > > https://sashiko.dev/#/patchset/20260630164143.1595669-1-usama.arif@linux.dev
> > > >
> > > >
> > >
> > > Hm, my understanding was that mm-new is where we take everything submitted for
> > > early testing?
> > >
> > > Did something change?
> >
> > mm-new has always been a few day front-end to mm-unstable. To protect
> > linux-next from brand new material. It serves no other purpose.
>
> Well it only serves a purpose if it gives us better testing.
>
> We have a CI running tests now though, Mike - is that predicated on material
> being in mm-new or does it just grab the email?
CI grabs patches from patchwork and tries to apply them to one of the three
bases: mm-unstable, mm-new or the latest Linus' commit merged into mm.git.
If patches apply, the other bases are not checked.
This patches applied cleanly to mm-unstable and successfully passed (at
least once :) )
https://github.com/linux-mm/linux-mm/actions/runs/28544575927/
> If the CI is just grabbing email I wonder whether there's much purpose in the
> mm-new branch at all.
I can't say that CI I run has a great coverage. I don't know what coverage
mm-new has though.
> Thanks, Lorenzo
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-07-02 13:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 16:34 [PATCH 0/6] mm: preparatory patches for PMD level swap entries Usama Arif
2026-06-30 16:34 ` [PATCH 1/6] mm: add softleaf_to_pmd() and convert existing callers Usama Arif
2026-06-30 16:34 ` [PATCH 2/6] mm: extract mm_prepare_for_swap_entries() helper Usama Arif
2026-07-01 16:56 ` David Hildenbrand (Arm)
2026-06-30 16:34 ` [PATCH 3/6] fs/proc: use softleaf_has_pfn() in pagemap PMD walker Usama Arif
2026-06-30 16:34 ` [PATCH 4/6] mm/huge_memory: move softleaf_to_folio() inside migration branch Usama Arif
2026-06-30 16:34 ` [PATCH 5/6] mm/migrate_device: move softleaf_to_folio() inside device-private branch Usama Arif
2026-07-01 19:40 ` David Hildenbrand (Arm)
2026-06-30 16:34 ` [PATCH 6/6] mm: rename ARCH_ENABLE_THP_MIGRATION to ARCH_SUPPORTS_PMD_SOFTLEAF Usama Arif
2026-07-01 20:03 ` David Hildenbrand (Arm)
2026-07-01 20:39 ` Zi Yan
2026-07-01 20:50 ` David Hildenbrand (Arm)
2026-07-01 20:55 ` Zi Yan
2026-07-02 16:55 ` Lorenzo Stoakes
2026-06-30 19:50 ` [PATCH 0/6] mm: preparatory patches for PMD level swap entries Andrew Morton
2026-07-01 8:04 ` Lorenzo Stoakes
2026-07-01 23:46 ` Andrew Morton
2026-07-02 10:48 ` Lorenzo Stoakes
2026-07-02 13:08 ` Mike Rapoport [this message]
2026-07-02 16:53 ` Lorenzo Stoakes
2026-07-02 16:57 ` Mark Brown
2026-07-02 17:08 ` Lorenzo Stoakes
2026-07-02 17:10 ` David Hildenbrand (Arm)
2026-07-02 17:21 ` Lorenzo Stoakes
2026-07-01 10:44 ` Usama Arif
2026-07-01 14:09 ` Usama Arif
2026-07-01 20:04 ` David Hildenbrand (Arm)
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=akZis7j6xSjl8K_D@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=kas@kernel.org \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=nphamcs@gmail.com \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=shikemeng@huaweicloud.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=youngjun.park@lge.com \
--cc=ziy@nvidia.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