From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Heiko Carstens <hca@linux.ibm.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Andreas Krebbel <krebbel@linux.ibm.com>,
Arnd Bergmann <arnd@arndb.de>, Willy Tarreau <w@1wt.eu>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH 4/8] tools: Remove s390 compat support
Date: Thu, 13 Nov 2025 16:43:59 +0100 [thread overview]
Message-ID: <72a8ffff-5074-4a7f-94ee-454c21f8a130@t-8ch.de> (raw)
In-Reply-To: <20251113150731.2697279-5-hca@linux.ibm.com>
On 2025-11-13 16:07:26+0100, Heiko Carstens wrote:
> Remove s390 compat support from everything within tools, since s390 compat
> support will be removed from the kernel.
>
> While removing s390 compat code replace __s390__ ifdef guards with
> __s390x__ everywhere. Even though this is not strictly required this
> makes it easier to spot s390 compat code support leftovers.
>
> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
> ---
> .../arch/s390/include/uapi/asm/bitsperlong.h | 4 --
Wouldn't it make sense to emit an explicit error from the UAPI
headers if a user tries to use them in 31-bit mode?
> tools/lib/bpf/libbpf.c | 4 --
> tools/lib/bpf/usdt.c | 2 -
> tools/include/nolibc/arch-s390.h | 5 ---
> tools/include/nolibc/arch.h | 2 +-
> .../testing/selftests/nolibc/Makefile.nolibc | 5 ---
> tools/testing/selftests/nolibc/run-tests.sh | 6 +--
Acked-by: Thomas Weißschuh <linux@weissschuh.net> # tools/nolibc selftests/nolibc
> tools/testing/selftests/rseq/rseq-s390.h | 39 -------------------
> tools/testing/selftests/vDSO/vdso_config.h | 4 --
Reviewed-by: Thomas Weißschuh <linux@weissschuh.net> # selftests/vDSO
> 9 files changed, 2 insertions(+), 69 deletions(-)
(...)
Thomas
next prev parent reply other threads:[~2025-11-13 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 15:07 [PATCH 0/8] s390: Remove " Heiko Carstens
2025-11-13 15:07 ` [PATCH 1/8] s390/ptrace: Rename psw_t32 to psw32_t Heiko Carstens
2025-11-13 15:28 ` Jimmy Brisson
2025-11-13 15:07 ` [PATCH 2/8] s390/kvm: Use psw32_t instead of psw_compat_t Heiko Carstens
2025-11-13 15:07 ` [PATCH 3/8] s390/syscalls: Add pt_regs parameter to SYSCALL_DEFINE0() syscall wrapper Heiko Carstens
2025-11-13 15:07 ` [PATCH 4/8] tools: Remove s390 compat support Heiko Carstens
2025-11-13 15:43 ` Thomas Weißschuh [this message]
2025-11-13 19:45 ` Heiko Carstens
2025-11-13 20:52 ` Alexei Starovoitov
2025-11-13 15:07 ` [PATCH 5/8] s390: Remove " Heiko Carstens
2025-11-13 15:07 ` [PATCH 6/8] s390/uapi: Remove 31 bit support from uapi header files Heiko Carstens
2025-11-13 15:07 ` [PATCH 7/8] s390/syscalls: Remove system call table pointer from thread_struct Heiko Carstens
2025-11-13 15:07 ` [PATCH 8/8] s390/syscalls: Switch to generic system call table generation Heiko Carstens
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=72a8ffff-5074-4a7f-94ee-454c21f8a130@t-8ch.de \
--to=linux@weissschuh.net \
--cc=agordeev@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=arnd@arndb.de \
--cc=ast@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=krebbel@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=svens@linux.ibm.com \
--cc=w@1wt.eu \
/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®