From: Mark Brown <broonie@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Willy Tarreau <w@1wt.eu>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h
Date: Fri, 23 May 2025 11:14:33 +0100 [thread overview]
Message-ID: <aDBKiafQmW8mGuN8@finisterre.sirena.org.uk> (raw)
In-Reply-To: <25a18e14-8ac9-4ac8-8907-a087050b1eb6@t-8ch.de>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On Fri, May 23, 2025 at 10:33:13AM +0200, Thomas Weißschuh wrote:
> On 2025-05-21 19:49:39+0100, Mark Brown wrote:
> > That seems to build with 869c788909b93a78ead1ca28c42b95eeb0779215 which
> > is the current HEAD of:
> > git://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git for-next
> Thanks for testing!
> To be sure, was this your full test-run? Or did you do a full test-run
Just a build of the arm64 selftests (which are the only thing I build
that was affected).
> on linux-next in the meantime?
> I'd like to get your confirmation before sending these changes to Linus.
Today's -next appears to have built and be running the arm64 selftests
OK again in my personal CI:
https://lava.sirena.org.uk/scheduler/job/1419721#L2482
There shoud also be results (both build and runtime) from KernelCI:
https://dashboard.kernelci.org/
but there might be a bit more lag seeing the results there.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-23 10:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 19:57 [PATCH 0/9] tools/nolibc: split out more headers Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 1/9] tools/nolibc: move ioctl() to sys/ioctl.h Thomas Weißschuh
2025-05-21 13:03 ` Mark Brown
2025-05-21 13:08 ` Thomas Weißschuh
2025-05-21 13:22 ` Mark Brown
2025-05-21 13:45 ` Thomas Weißschuh
2025-05-21 13:58 ` Mark Brown
2025-05-21 18:49 ` Mark Brown
2025-05-23 8:33 ` Thomas Weißschuh
2025-05-23 10:14 ` Mark Brown [this message]
2025-05-15 19:57 ` [PATCH 2/9] tools/nolibc: move mount() to sys/mount.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 3/9] tools/nolibc: move prctl() to sys/prctl.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 4/9] tools/nolibc: move reboot() to sys/reboot.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 5/9] tools/nolibc: move getrlimit() and friends to sys/resource.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 6/9] tools/nolibc: move makedev() and friends to sys/sysmacros.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 7/9] tools/nolibc: move uname() and friends to sys/utsname.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 8/9] tools/nolibc: move NULL and offsetof() to sys/stddef.h Thomas Weißschuh
2025-05-15 19:57 ` [PATCH 9/9] selftests/nolibc: drop include guards around standard headers Thomas Weißschuh
2025-05-16 3:50 ` [PATCH 0/9] tools/nolibc: split out more headers Willy Tarreau
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=aDBKiafQmW8mGuN8@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.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®