From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
Muchun Song <muchun.song@linux.dev>
Cc: Muchun Song <songmuchun@bytedance.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Qi Zheng <qi.zheng@linux.dev>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 0/6] mm: Unify device DAX and HugeTLB vmemmap population paths
Date: Mon, 28 Sep 2026 21:03:57 +0200 [thread overview]
Message-ID: <e36e8b24-81fc-45c7-8eb9-8b363e3d89be@kernel.org> (raw)
In-Reply-To: <se2tjmpk.ritesh.list@gmail.com>
On 9/28/26 19:43, Ritesh Harjani (IBM) wrote:
> Muchun Song <muchun.song@linux.dev> writes:
>
>>
>> If you're planning to review this series, I'd suggest waiting for my rebased
>> version.
>>
>
> Hello Muchun,
>
> Thanks for taking care of powerpc side of the changes. Is it possible to
> share your git/github tree somewhere? Sorry, but it's hard to follow
> which series is based on which and the overall multi-series is based on
> which upstream tree. If you could share your updated tree somewhere -
> that would make my life simpler.
Yes, that usually helps. And next time better clearly spell out the current list
of series, where they currently are (mm-new, mm-unstable, on list etc) and the
dependencies.
I was a bit confused :)
--
Cheers,
David
next prev parent reply other threads:[~2026-09-28 19:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 7:52 Muchun Song
2026-09-24 7:52 ` [PATCH v2 1/6] mm/sparse-vmemmap: drop VMEMMAP_POPULATE_DAX Muchun Song
2026-09-24 7:52 ` [PATCH v2 2/6] mm/sparse-vmemmap: support device DAX in common vmemmap path Muchun Song
2026-09-28 1:49 ` Qi Zheng
2026-09-24 7:52 ` [PATCH v2 3/6] mm/sparse-vmemmap: drop Device DAX-specific population path Muchun Song
2026-09-24 7:52 ` [PATCH v2 4/6] mm/sparse-vmemmap: remove the unused ptpfn argument Muchun Song
2026-09-24 7:52 ` [PATCH v2 5/6] mm/sparse-vmemmap: open-code vmemmap_populate_address() Muchun Song
2026-09-24 7:52 ` [PATCH v2 6/6] mm/mm_init: add zone mismatch warning during page init Muchun Song
2026-09-28 1:59 ` Qi Zheng
2026-09-28 12:44 ` [PATCH v2 0/6] mm: Unify device DAX and HugeTLB vmemmap population paths David Hildenbrand (Arm)
2026-09-28 13:49 ` Muchun Song
2026-09-28 17:43 ` Ritesh Harjani
2026-09-28 19:03 ` David Hildenbrand (Arm) [this message]
2026-09-29 0:51 ` Muchun Song
2026-09-29 0:57 ` Muchun Song
2026-09-29 1:57 ` Ritesh Harjani
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=e36e8b24-81fc-45c7-8eb9-8b363e3d89be@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=npiggin@gmail.com \
--cc=qi.zheng@linux.dev \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=vbabka@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
all inboxes | Powered by JetHome®