From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] selftests/nolibc: don't skip tests for unimplemented syscalls anymore
Date: Tue, 7 Apr 2026 09:21:17 +0200 [thread overview]
Message-ID: <adSwbcx_0FWWqeIP@1wt.eu> (raw)
In-Reply-To: <20260406-nolibc-no-skip-enosys-v1-0-c046b1ac7d73@weissschuh.net>
On Mon, Apr 06, 2026 at 10:02:36PM +0200, Thomas Weißschuh wrote:
> The automatic skipping of tests on ENOSYS returns was introduced in
> commit 349afc8a52f8 ("selftests/nolibc: skip tests for unimplemented
> syscalls"). It handled the fact that nolibc would return ENOSYS for many
> syscall wrappers on riscv32.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Acked-by: Willy Tarreau <w@1wt.eu>
thanks!
Willy
prev parent reply other threads:[~2026-04-07 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 20:02 [PATCH 0/2] selftests/nolibc: don't skip tests for unimplemented syscalls anymore Thomas Weißschuh
2026-04-06 20:02 ` [PATCH 1/2] selftests/nolibc: explicitly handle ENOSYS from ptrace() Thomas Weißschuh
2026-04-06 20:02 ` [PATCH 2/2] selftests/nolibc: don't skip tests for unimplemented syscalls anymore Thomas Weißschuh
2026-04-07 7:21 ` Willy Tarreau [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=adSwbcx_0FWWqeIP@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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