[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3e0ea1fb-e16d-4a63-9991-fde6a146f07d@linuxfoundation.org>
Date: Mon, 11 Dec 2023 08:26:00 -0700
From: Shuah Khan <skhan@...uxfoundation.org>
To: paulmck@...nel.org,
Thomas Weißschuh <linux@...ssschuh.net>
Cc: linux-kernel@...r.kernel.org, WillyTarreauw@....eu,
Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: nolibc changes for 6.8
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
Powered by blists - more mailing lists