Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] lapi: Update syscalls numbers to v7.3-rc5
Date: Tue, 29 Sep 2026 17:59:35 +0200	[thread overview]
Message-ID: <20260929155935.GB2614679@pevik> (raw)
In-Reply-To: <20260929141659.2513510-1-pvorel@suse.cz>

Hi all,

> Updating syscalls should help fixing issue with sparc not working on
> tst_clone().

> Reported-by: Anders Roxell <anders.roxell@linaro.org>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
> ---
> It should be safe, but do we dare to merge before LTP release?

> This tries to avoid workaround for sparc()
> https://patchwork.kernel.org/project/ltp/patch/20260929084253.3093742-1-anders.roxell@linaro.org/
> https://lore.kernel.org/ltp/20260929084253.3093742-1-anders.roxell@linaro.org/

>  include/lapi/syscalls/arc.in         |   3 +
>  include/lapi/syscalls/arm.in         |   4 +-
>  include/lapi/syscalls/arm64.in       |   3 +
>  include/lapi/syscalls/i386.in        |   4 +-
>  include/lapi/syscalls/loongarch64.in |   3 +
>  include/lapi/syscalls/mips64.in      |   5 +-
>  include/lapi/syscalls/mips64n32.in   |   5 +-
>  include/lapi/syscalls/mipso32.in     |   5 +-
>  include/lapi/syscalls/parisc.in      |   4 +-
>  include/lapi/syscalls/powerpc.in     |   4 +-
>  include/lapi/syscalls/powerpc64.in   |   4 +-
>  include/lapi/syscalls/s390.in        | 103 +++++++--------------------

Hm, this removes s390 31 bit support, which was removed in v6.19-rc1
8e0b986c59c67 ("s390: Remove compat support")

Quoting the commit message, it gives me confidence, that nobody will miss these
syscall numbers. But I should note that into the commit message.

Kind regards,
Petr

	There shouldn't be any 31 bit code around anymore that matters.
	Remove the compat layer support required to run 31 bit code.

	Reason for removal is code simplification and reduced test effort.

	Note that this comes without any deprecation warnings added to config
	options, or kernel messages, since most likely those would be ignored
	anyway.

	If it turns out there is still a reason to keep the compat layer this
	can be reverted at any time in the future.

>  include/lapi/syscalls/s390x.in       |   5 +-
>  include/lapi/syscalls/sh.in          |   4 +-
>  include/lapi/syscalls/sparc.in       |   5 +-
>  include/lapi/syscalls/sparc64.in     |   5 +-
>  include/lapi/syscalls/x86_64.in      |   5 +-
>  17 files changed, 77 insertions(+), 94 deletions(-)

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-09-29 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 14:16 [LTP] [PATCH 1/1] lapi: Update syscalls numbers to v7.3-rc5 Petr Vorel
2026-09-29 15:59 ` Petr Vorel [this message]
2026-09-30  7:45   ` Andrea Cervesato via ltp
2026-09-30  8:59     ` Petr Vorel
2026-09-30  9:56       ` Andrea Cervesato via ltp
2026-09-29 17:51 ` [LTP] " linuxtestproject.agent

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=20260929155935.GB2614679@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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