From: Shuah Khan <skhan@linuxfoundation.org>
To: paulmck@kernel.org, "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kernel@vger.kernel.org, WillyTarreauw@lwt.eu,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: nolibc changes for 6.8
Date: Mon, 11 Dec 2023 08:26:00 -0700 [thread overview]
Message-ID: <3e0ea1fb-e16d-4a63-9991-fde6a146f07d@linuxfoundation.org> (raw)
In-Reply-To: <25a20ebe-e5af-4ba7-890a-6a9ab121e184@paulmck-laptop>
On 12/8/23 17:02, Paul E. McKenney wrote:
> On Fri, Dec 08, 2023 at 06:09:59PM +0100, Thomas Weißschuh wrote:
>> Hi Paul,
>>
>> The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:
>>
>> Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)
>>
>> are available in the Git repository at:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/nolibc/linux-nolibc.git/ next
>>
>> for you to fetch changes up to b99c3b15310e7c7cd5f2d843289fe115ab3f8043:
>>
>> selftests/nolibc: disable coredump via setrlimit (2023-11-26 11:39:52 +0100)
>
> Thank you!
>
> I pulled this in and got the following:
>
> make run:
> 162 test(s): 162 passed, 0 skipped, 0 failed => status: success
>
> make run-user:
> 162 test(s): 160 passed, 2 skipped, 0 failed => status: warning
>
> This looks like complete success to me, but please let me know if this
> is not expected behavior on an x86-64 laptop.
>
Paul,
This is my turn to send the pull request. Would you like
me to take care of it?
thanks,
-- Shuah
next prev parent reply other threads:[~2023-12-11 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:09 nolibc changes for 6.8 Thomas Weißschuh
2023-12-09 0:02 ` Paul E. McKenney
2023-12-09 8:27 ` Thomas Weißschuh
2023-12-11 15:26 ` Shuah Khan [this message]
2023-12-11 16:20 ` Paul E. McKenney
2023-12-11 19:52 ` Shuah Khan
2023-12-11 21:40 ` Thomas Weißschuh
2023-12-11 23:49 ` Shuah Khan
2023-12-12 15:31 ` Shuah Khan
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=3e0ea1fb-e16d-4a63-9991-fde6a146f07d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=WillyTarreauw@lwt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@kernel.org \
/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