From: Helge Deller <deller@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-parisc@vger.kernel.org,
John David Anglin <dave.anglin@bell.net>
Subject: [GIT PULL] parisc architecture fixes and updates for v7.1-rc1
Date: Sat, 18 Apr 2026 17:50:08 +0200 [thread overview]
Message-ID: <aeOoMH5JI2wjFQrZ@p100> (raw)
Hi Linus,
please pull fixes and updates for parisc for kernel 7.1-rc1.
One important fix to unbreak modules on 32-bit parisc, which were broken
since kernel v6.19. The other changes are just smaller maintenance cleanups.
Thanks!
Helge
----------------------------------------------------------------
The following changes since commit 43cfbdda5af60ffc6272a7b8c5c37d1d0a181ca9:
Merge tag 'for-linus-iommufd' of git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd (2026-04-16 21:21:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git tags/parisc-for-7.1-rc1
for you to fetch changes up to 707610bcccbd0327530938e33f3f33211a640a4e:
parisc: led: fix reference leak on failed device registration (2026-04-17 15:46:46 +0200)
----------------------------------------------------------------
parisc architecture fixes and updates for kernel v7.1-rc1:
- A fix to make modules on 32-bit parisc architecture work again
- Drop ip_fast_csum() inline assembly to avoid unaligned memory accesses
- Allow to build kernel without 32-bit VDSO
- Reference leak fix in error path in LED driver
----------------------------------------------------------------
Guangshuo Li (1):
parisc: led: fix reference leak on failed device registration
Helge Deller (10):
parisc: Drop ip_fast_csum() inline assembly implementation
parisc: _llseek syscall is only available for 32-bit userspace
parisc: Avoid compat syscalls when COMPAT=n
parisc: is_compat_task() shall return false for COMPAT=n
parisc: Fix signal code to depend on CONFIG_COMPAT instead of CONFIG_64BIT
parisc: Fix default stack size when COMPAT=n
parisc: Allow to disable COMPAT mode on 64-bit kernel
parisc: Include 32-bit VDSO only when building for 32-bit or compat mode
parisc: Allow to build without VDSO32
module.lds.S: Fix modules on 32-bit parisc architecture
Kexin Sun (1):
parisc: update outdated comments for renamed ccio_alloc_consistent()
arch/Kconfig | 7 +++
arch/parisc/Kconfig | 7 ++-
arch/parisc/Makefile | 6 +-
arch/parisc/include/asm/checksum.h | 89 +----------------------------
arch/parisc/include/asm/compat.h | 2 +-
arch/parisc/include/asm/vdso.h | 2 +
arch/parisc/kernel/Makefile | 3 +-
arch/parisc/kernel/signal.c | 18 +++---
arch/parisc/kernel/sys_parisc.c | 4 ++
arch/parisc/kernel/syscall.S | 11 ++--
arch/parisc/kernel/syscalls/syscall.tbl | 2 +-
arch/parisc/lib/Makefile | 2 +-
arch/parisc/lib/checksum.c | 99 ---------------------------------
drivers/parisc/ccio-dma.c | 8 +--
drivers/parisc/led.c | 6 +-
scripts/module.lds.S | 2 +
16 files changed, 56 insertions(+), 212 deletions(-)
delete mode 100644 arch/parisc/lib/checksum.c
next reply other threads:[~2026-04-18 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 15:50 Helge Deller [this message]
2026-04-18 18:40 ` [GIT PULL] parisc architecture fixes and updates for v7.1-rc1 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=aeOoMH5JI2wjFQrZ@p100 \
--to=deller@kernel.org \
--cc=dave.anglin@bell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.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