From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Paul E. McKenney" <paulmck@kernel.org>
Cc: Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [GIT PULL] nolibc for 6.11-rc1
Date: Mon, 15 Jul 2024 09:50:12 -0600 [thread overview]
Message-ID: <5cccbde4-b296-4759-9ae4-bf1b65f24c5b@linuxfoundation.org> (raw)
In-Reply-To: <fdf4c2b8-dab7-40f0-a595-fd4f2108964e@t-8ch.de>
On 7/15/24 01:00, Thomas Weißschuh wrote:
> On 2024-07-14 09:44:55+0000, Paul E. McKenney wrote:
>> On Sun, Jul 14, 2024 at 10:09:13AM +0200, Thomas Weißschuh wrote:
>>> On 2024-07-12 20:16:13+0000, Paul E. McKenney wrote:
>>>> On Sun, Jun 30, 2024 at 09:06:39AM -0700, Paul E. McKenney wrote:
>>>>> On Sat, Jun 29, 2024 at 01:04:08PM +0200, Thomas Weißschuh wrote:
>>>>>> Hi Paul,
>>>>>>
>>>>>> The following changes since commit f2661062f16b2de5d7b6a5c42a9a5c96326b8454:
>>>>>>
>>>>>> Linux 6.10-rc5 (2024-06-23 17:08:54 -0400)
>>>>>>
>>>>>> are available in the Git repository at:
>>>>>>
>>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git tags/nolibc-20240629-for-6.11-1
>>>>>>
>>>>>> for you to fetch changes up to 6ca8f2e20bd1ced8a7cd12b3ae4b1ceca85cfc2b:
>>>>>>
>>>>>> selftests: kselftest: also use strerror() on nolibc (2024-06-29 09:44:58 +0200)
>>>>>
>>>>> Hearing no objections, I have pulled this in so that it will appear
>>>>> in the next -next. Here are the test results:
>>>>>
>>>>> make run:
>>>>> 195 test(s): 195 passed, 0 skipped, 0 failed => status: success
>>>>>
>>>>> make run-user:
>>>>> 195 test(s): 193 passed, 2 skipped, 0 failed => status: warning
>>>>>
>>>>> So looks good to me!
>>>
>>> For testing you can use "./run-tests.sh -m [user | system]" to run the
>>> tests on all supported architectures via QEMU.
>>>
>>> (On the first run you can use "-p" to download the toolchains)
>>
>> Thank you for the info!
>>
>> My near-term plan is that I do a smoke test on x86 (or whatever I am
>> running), and let you guys cover the various architectures. Longer
>> term, I might get more into cross-architecture work.
>
Thank for fielding this time. Next one in on me.
> I'll try to remember to add the full testreport for future
> pullrequests, too.
>
Thanks - that will be great.
I run the nolibc tests before I send PR - I also compare to see if my
results match with yours.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-07-15 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-29 11:04 Thomas Weißschuh
2024-06-30 16:06 ` Paul E. McKenney
2024-07-13 3:16 ` Paul E. McKenney
2024-07-14 4:57 ` Willy Tarreau
2024-07-14 15:57 ` Paul E. McKenney
2024-07-14 8:09 ` Thomas Weißschuh
2024-07-14 16:44 ` Paul E. McKenney
2024-07-15 7:00 ` Thomas Weißschuh
2024-07-15 15:50 ` Shuah Khan [this message]
2024-07-15 21:27 ` Paul E. McKenney
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=5cccbde4-b296-4759-9ae4-bf1b65f24c5b@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@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®