From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Lorenzo Stoakes <ljs@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Usama Arif <usama.arif@linux.dev>,
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 19:10:34 +0200 [thread overview]
Message-ID: <756f3fb7-5129-435f-a84e-a2af48e323ab@kernel.org> (raw)
In-Reply-To: <akaawVcQ4D4XSOKs@lucifer>
On 7/2/26 19:08, Lorenzo Stoakes wrote:
> On Thu, Jul 02, 2026 at 05:57:34PM +0100, Mark Brown wrote:
>> On Thu, Jul 02, 2026 at 05:53:48PM +0100, Lorenzo Stoakes wrote:
>>
>>
>>> Well we're very grateful for what coverage it has :) and that's nice to have it
>>> work with email like that also, makes life simpler.
>>
>>> Mark - are you running tests based on mm-new? I'm not sure where things stand on
>>> that?
>>
>> I currently test -next, mainline and stable plus my own stuff.
>
> Ack thanks!
>
> I guess in the long run then we can figure out a way to not necessarily even
> require mm-new at all, and instead let our CI try to handle as much as it can
> before -> linux-next :)
>
> As that'd be the nicest way and help reduce confusion about branches for
> mm-next.
If we go the for-test route, we'd still have a branch where people/bots/tools
can do more elaborate tests when throwing stuff together. I still consider that
reasonable, but we'll have to see if we really need that.
--
Cheers,
David
next prev parent reply other threads:[~2026-07-02 17:10 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
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) [this message]
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=756f3fb7-5129-435f-a84e-a2af48e323ab@kernel.org \
--to=david@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=broonie@kernel.org \
--cc=chrisl@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=rppt@kernel.org \
--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