From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] nolibc changes for v6.15
Date: Mon, 10 Mar 2025 10:09:49 -0700 [thread overview]
Message-ID: <00c760a8-0075-486f-9456-63ae07ecb341@paulmck-laptop> (raw)
In-Reply-To: <25e1c397-d554-4334-b344-56ec252564c1@t-8ch.de>
On Sat, Mar 08, 2025 at 02:06:21PM +0100, Thomas Weißschuh wrote:
> Hi Paul,
>
> The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
>
> Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git tags/nolibc-20250308-for-6.15-1
>
> for you to fetch changes up to bceb73904c855c78402dca94c82915f078f259dd:
>
> tools/nolibc: don't use asm/ UAPI headers (2025-03-08 13:18:27 +0100)
Thank you, I have pulled this in and will expose it to -next testing.
Results from "make run":
198 test(s): 198 passed, 0 skipped, 0 failed => status: success
Results from "make user":
198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
I don't understand the "warning" given that the "run.out" file has all
"OK" aside from the two "SKIPPED" tests. Or maybe I am just forgetting
how this works. ;-)
Thanx, Paul
> ----------------------------------------------------------------
> nolibc changes for 6.15
>
> Changes
> -------
>
> * 32bit s390 support
> * opendir()/readdir_r()/closedir() support
> * openat() support
> * sscanf() support
> * various cleanups
>
> ----------------------------------------------------------------
> Louis Taylor (5):
> tools/nolibc: add support for openat(2)
> tools/nolibc: always use openat(2) instead of open(2)
> tools/nolibc: process open() vararg as mode_t
> tools/nolibc: drop outdated example from overview comment
> selftests/nolibc: use O_RDONLY flag instead of 0
>
> Thomas Weißschuh (21):
> tools/nolibc: add prototypes for non-static functions
> selftests/nolibc: ignore -Wmissing-prototypes
> selftests/nolibc: enable -Wmissing-prototypes
> tools/nolibc: make signature of ioctl() more flexible
> selftests/nolibc: drop mips32be EXTRACONFIG
> selftests/nolibc: drop call to prepare target
> selftests/nolibc: drop call to mrproper target
> selftests/nolibc: execute defconfig before other targets
> selftests/nolibc: always keep test kernel configuration up to date
> tools/nolibc: add support for sys_llseek()
> tools/nolibc: add support for directory access
> selftests/nolibc: split up architecture list in run-tests.sh
> selftests/nolibc: only run constructor tests on nolibc
> selftests/nolibc: rename s390 to s390x
> tools/nolibc: add support for 32-bit s390
> tools/nolibc: add support for [v]sscanf()
> Revert "selftests: kselftest: Fix build failure with NOLIBC"
> selftests/nolibc: explicitly enable ARM mode
> selftests/nolibc: add armthumb configuration
> selftests/nolibc: stop testing constructor order
> tools/nolibc: don't use asm/ UAPI headers
>
> tools/include/nolibc/Makefile | 1 +
> tools/include/nolibc/arch-mips.h | 1 +
> tools/include/nolibc/arch-s390.h | 9 +-
> tools/include/nolibc/arch.h | 2 +-
> tools/include/nolibc/crt.h | 2 +
> tools/include/nolibc/dirent.h | 98 +++++++++++++++
> tools/include/nolibc/errno.h | 2 +-
> tools/include/nolibc/nolibc.h | 4 +-
> tools/include/nolibc/signal.h | 1 +
> tools/include/nolibc/stackprotector.h | 2 +
> tools/include/nolibc/stdio.h | 98 +++++++++++++++
> tools/include/nolibc/stdlib.h | 1 +
> tools/include/nolibc/string.h | 4 +
> tools/include/nolibc/sys.h | 83 +++++++++----
> tools/testing/selftests/kselftest.h | 5 -
> tools/testing/selftests/nolibc/Makefile | 30 +++--
> .../testing/selftests/nolibc/nolibc-test-linkage.c | 6 +-
> tools/testing/selftests/nolibc/nolibc-test.c | 138 ++++++++++++++++++++-
> tools/testing/selftests/nolibc/run-tests.sh | 26 +++-
> 19 files changed, 457 insertions(+), 56 deletions(-)
> create mode 100644 tools/include/nolibc/dirent.h
>
> Test results:
>
> $ ./run-tests.sh
> i386: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> x86_64: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> arm64: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> arm: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> armthumb: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> mips32le: 198 test(s): 197 passed, 1 skipped, 0 failed => status: warning
> mips32be: 198 test(s): 197 passed, 1 skipped, 0 failed => status: warning
> ppc: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> ppc64: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> ppc64le: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> riscv32: 198 test(s): 183 passed, 15 skipped, 0 failed => status: warning
> riscv64: 198 test(s): 198 passed, 0 skipped, 0 failed => status: success
> s390x: 198 test(s): 197 passed, 1 skipped, 0 failed => status: warning
> s390: 198 test(s): 197 passed, 1 skipped, 0 failed => status: warning
> loongarch: 198 test(s): 197 passed, 1 skipped, 0 failed => status: warning
>
> $ ./run-tests.sh -m user -l
> i386: 198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
> x86_64: 198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
> arm64: 198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
> arm: 198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
> armthumb: 198 test(s): 196 passed, 2 skipped, 0 failed => status: warning
> mips32le: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> mips32be: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> ppc: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> ppc64: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> ppc64le: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> riscv32: 198 test(s): 180 passed, 18 skipped, 0 failed => status: warning
> riscv64: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> s390x: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
> s390: Unsupported configuration
> loongarch: 198 test(s): 195 passed, 3 skipped, 0 failed => status: warning
>
> Thanks,
> Thomas
next prev parent reply other threads:[~2025-03-10 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 13:06 Thomas Weißschuh
2025-03-10 17:09 ` Paul E. McKenney [this message]
2025-03-10 18:22 ` Thomas Weißschuh
2025-03-10 18:55 ` Paul E. McKenney
2025-03-21 23:19 Paul E. McKenney
2025-03-25 1:58 ` 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=00c760a8-0075-486f-9456-63ae07ecb341@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=skhan@linuxfoundation.org \
--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®