From: patchwork-bot+linux-riscv@kernel.org
To: Muchun Song <songmuchun@bytedance.com>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
david@kernel.org, catalin.marinas@arm.com, will@kernel.org,
palmer@dabbelt.com, pjw@kernel.org, chenhuacai@kernel.org,
andreas@gaisler.com, davem@davemloft.net, muchun.song@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, loongarch@lists.linux.dev,
sparclinux@vger.kernel.org, alex@ghiti.fr, aou@eecs.berkeley.edu,
kernel@xen0n.name, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
mhocko@suse.com
Subject: Re: [PATCH v3 0/5] mm/sparse-vmemmap: Provide generic vmemmap_set_pmd() and vmemmap_check_pmd()
Date: Fri, 26 Jun 2026 08:21:17 +0000 [thread overview]
Message-ID: <178246207775.3816447.6521226918403076772.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260601084845.3792171-1-songmuchun@bytedance.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Mon, 1 Jun 2026 16:48:39 +0800 you wrote:
> The weak vmemmap_set_pmd() and vmemmap_check_pmd() hooks are
> currently no-ops in the generic code, which leaves architectures that
> need PMD-level handling to open-code the same logic locally.
>
> This series provides generic implementations for both helpers in
> mm/sparse-vmemmap.c. vmemmap_set_pmd() installs a huge PMD with
> PAGE_KERNEL protection, and vmemmap_check_pmd() verifies a present
> leaf PMD before reusing the existing vmemmap_verify() helper.
>
> [...]
Here is the summary with links:
- [v3,1/5] mm/sparse-vmemmap: provide generic vmemmap_set_pmd() and vmemmap_check_pmd()
https://git.kernel.org/riscv/c/0b6073ff1574
- [v3,2/5] arm64/mm: drop vmemmap_pmd helpers and use generic code
https://git.kernel.org/riscv/c/f521f198b50a
- [v3,3/5] riscv/mm: drop vmemmap_pmd helpers and use generic code
https://git.kernel.org/riscv/c/abff0ecf7602
- [v3,4/5] loongarch/mm: drop vmemmap_check_pmd helper and use generic code
https://git.kernel.org/riscv/c/ecca7da924b1
- [v3,5/5] sparc/mm: drop vmemmap_check_pmd helper and use generic code
https://git.kernel.org/riscv/c/d3d58e946900
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-26 8:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 8:48 [PATCH v3 0/5] mm/sparse-vmemmap: Provide generic vmemmap_set_pmd() and vmemmap_check_pmd() Muchun Song
2026-06-01 8:48 ` [PATCH v3 1/5] mm/sparse-vmemmap: provide " Muchun Song
2026-06-01 12:22 ` David Hildenbrand (Arm)
2026-06-01 12:37 ` Muchun Song
2026-06-02 4:40 ` Oscar Salvador (SUSE)
2026-06-02 4:41 ` Oscar Salvador (SUSE)
2026-06-01 8:48 ` [PATCH v3 2/5] arm64/mm: drop vmemmap_pmd helpers and use generic code Muchun Song
2026-06-01 12:23 ` David Hildenbrand (Arm)
2026-06-02 4:42 ` Oscar Salvador (SUSE)
2026-06-01 8:48 ` [PATCH v3 3/5] riscv/mm: " Muchun Song
2026-06-01 12:23 ` David Hildenbrand (Arm)
2026-06-02 4:44 ` Oscar Salvador (SUSE)
2026-06-01 8:48 ` [PATCH v3 4/5] loongarch/mm: drop vmemmap_check_pmd helper " Muchun Song
2026-06-01 12:24 ` David Hildenbrand (Arm)
2026-06-01 12:26 ` Muchun Song
2026-06-02 4:45 ` Oscar Salvador (SUSE)
2026-06-01 8:48 ` [PATCH v3 5/5] sparc/mm: " Muchun Song
2026-06-01 12:25 ` David Hildenbrand (Arm)
2026-06-02 4:46 ` Oscar Salvador (SUSE)
2026-06-26 8:21 ` patchwork-bot+linux-riscv [this message]
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=178246207775.3816447.6521226918403076772.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=andreas@gaisler.com \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=davem@davemloft.net \
--cc=david@kernel.org \
--cc=kernel@xen0n.name \
--cc=liam@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=ljs@kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.com \
--cc=sparclinux@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=will@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