From: "Thomas Weißschuh" <linux@weissschuh.net>
To: "Paul E. McKenney" <paulmck@kernel.org>
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 19:22:35 +0100 [thread overview]
Message-ID: <3598f2c8-e04a-4e4a-ae1f-db2201fff802@t-8ch.de> (raw)
In-Reply-To: <00c760a8-0075-486f-9456-63ae07ecb341@paulmck-laptop>
On 2025-03-10 10:09:49-0700, Paul E. McKenney wrote:
> On Sat, Mar 08, 2025 at 02:06:21PM +0100, Thomas Weißschuh wrote:
> > 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.
Thanks!
> 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. ;-)
A skipped test will mark the whole run as "warning".
Maybe we'll adopt the kselftest harness at some point and align with the
rest of the selftests.
<snip>
Thomas
next prev parent reply other threads:[~2025-03-10 18:22 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
2025-03-10 18:22 ` Thomas Weißschuh [this message]
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=3598f2c8-e04a-4e4a-ae1f-db2201fff802@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--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®