From: Paul Walmsley <pjw@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V updates for v6.17-rc8
Date: Fri, 26 Sep 2025 12:33:10 -0600 (MDT) [thread overview]
Message-ID: <c6ef1683-9c29-cb02-4498-31fce8934d9e@kernel.org> (raw)
Linus,
The following changes since commit a03ee11b8f850bd008226c6d392da24163dfb56e:
riscv: Fix sparse warning about different address spaces (2025-09-05 15:33:52 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux tags/riscv-for-linus-v6.17-rc8
for you to fetch changes up to e24108012ce9662d90093f91d5ffebcbf78da7de:
MAINTAINERS: Update Paul Walmsley's E-mail address (2025-09-23 20:18:45 -0600)
----------------------------------------------------------------
RISC-V fixes for v6.17-rc8
Two small RISC-V fixes for v6.17-rc8:
- A race-free implementation of pudp_huge_get_and_clear() (based on the x86
code)
- A MAINTAINERS update to my E-mail address
----------------------------------------------------------------
Alexandre Ghiti (1):
riscv: Use an atomic xchg in pudp_huge_get_and_clear()
Paul Walmsley (1):
MAINTAINERS: Update Paul Walmsley's E-mail address
MAINTAINERS | 8 ++++----
arch/riscv/include/asm/pgtable.h | 17 +++++++++++++++++
2 files changed, 21 insertions(+), 4 deletions(-)
text data bss dec hex filename
12772113 6174050 419253 19365416 1277e28 vmlinux.rv64.orig
12772113 6174050 419253 19365416 1277e28 vmlinux.rv64
11725507 5994478 404229 18124214 1148db6 vmlinux.rv64_nosmp.orig
11725507 5994478 404229 18124214 1148db6 vmlinux.rv64_nosmp
11723502 4702754 309629 16735885 ff5e8d vmlinux.rv32.orig
11723502 4702754 309629 16735885 ff5e8d vmlinux.rv32
2612497 761072 119048 3492617 354b09 vmlinux.nommu_virt.orig
2612497 761072 119048 3492617 354b09 vmlinux.nommu_virt
next reply other threads:[~2025-09-26 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 18:33 Paul Walmsley [this message]
2025-09-26 21:44 ` pr-tracker-bot
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=c6ef1683-9c29-cb02-4498-31fce8934d9e@kernel.org \
--to=pjw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=torvalds@linux-foundation.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®