From: patchwork-bot+linux-riscv@kernel.org
To: Chunyan Zhang <zhangchunyan@iscas.ac.cn>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
robh@kernel.org, krzk+dt@kernel.org, conor@kernel.org,
debug@rivosinc.com, ved@rivosinc.com, viro@zeniv.linux.org.uk,
brauner@kernel.org, jack@suse.cz, akpm@linux-foundation.org,
peterx@redhat.com, arnd@arndb.de, david@redhat.com,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
vbabka@suse.cz, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, axelrasmussen@google.com, yuanchu@google.com,
zhang.lyra@gmail.com
Subject: Re: [PATCH V14 0/6] riscv: mm: Add soft-dirty and uffd-wp support
Date: Fri, 19 Dec 2025 08:09:56 +0000 [thread overview]
Message-ID: <176613179607.3684357.9882444672528861382.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250918083731.1820327-1-zhangchunyan@iscas.ac.cn>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Thu, 18 Sep 2025 16:37:25 +0800 you wrote:
> This patchset adds support for Svrsw60t59b [1] extension which is ratified now,
> also add soft dirty and userfaultfd write protect tracking for RISC-V.
>
> The patches 1 and 2 add macros to allow architectures to define their own checks
> if the soft-dirty / uffd_wp PTE bits are available, in other words for RISC-V,
> the Svrsw60t59b extension is supported on which device the kernel is running.
> Also patch1-2 are removing "ifdef CONFIG_MEM_SOFT_DIRTY"
> "ifdef CONFIG_HAVE_ARCH_USERFAULTFD_WP" and
> "ifdef CONFIG_PTE_MARKER_UFFD_WP" in favor of checks which if not overridden by
> the architecture, no change in behavior is expected.
>
> [...]
Here is the summary with links:
- [V14,1/6] mm: softdirty: Add pgtable_supports_soft_dirty()
(no matching commit)
- [V14,2/6] mm: userfaultfd: Add pgtable_supports_uffd_wp()
(no matching commit)
- [V14,3/6] riscv: Add RISC-V Svrsw60t59b extension support
https://git.kernel.org/riscv/c/59f6acb4be02
- [V14,4/6] riscv: mm: Add soft-dirty page tracking support
https://git.kernel.org/riscv/c/2a3ebad4db63
- [V14,5/6] riscv: mm: Add userfaultfd write-protect support
https://git.kernel.org/riscv/c/c64da3950cf4
- [V14,6/6] dt-bindings: riscv: Add Svrsw60t59b extension description
https://git.kernel.org/riscv/c/519912bdaee8
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:[~2025-12-19 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 8:37 Chunyan Zhang
2025-09-18 8:37 ` [PATCH V14 1/6] mm: softdirty: Add pgtable_supports_soft_dirty() Chunyan Zhang
2025-09-18 9:03 ` David Hildenbrand
2025-09-18 8:37 ` [PATCH V14 2/6] mm: userfaultfd: Add pgtable_supports_uffd_wp() Chunyan Zhang
2025-09-18 8:37 ` [PATCH V14 3/6] riscv: Add RISC-V Svrsw60t59b extension support Chunyan Zhang
2025-09-18 8:37 ` [PATCH V14 4/6] riscv: mm: Add soft-dirty page tracking support Chunyan Zhang
2025-09-18 8:37 ` [PATCH V14 5/6] riscv: mm: Add userfaultfd write-protect support Chunyan Zhang
2025-09-18 8:37 ` [PATCH V14 6/6] dt-bindings: riscv: Add Svrsw60t59b extension description Chunyan Zhang
2025-09-18 15:14 ` Conor Dooley
2025-12-19 8:09 ` 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=176613179607.3684357.9882444672528861382.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=axelrasmussen@google.com \
--cc=brauner@kernel.org \
--cc=conor@kernel.org \
--cc=david@redhat.com \
--cc=debug@rivosinc.com \
--cc=devicetree@vger.kernel.org \
--cc=jack@suse.cz \
--cc=krzk+dt@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterx@redhat.com \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ved@rivosinc.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yuanchu@google.com \
--cc=zhang.lyra@gmail.com \
--cc=zhangchunyan@iscas.ac.cn \
/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