[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a699b6d0-f028-43d1-93c9-250b6c8c4a6b@linuxfoundation.org>
Date: Mon, 12 May 2025 15:32:40 -0600
From: Shuah Khan <skhan@...uxfoundation.org>
To: Thomas Weißschuh <linux@...ssschuh.net>,
Shuah Khan <shuah@...nel.org>, Kees Cook <kees@...nel.org>
Cc: Thomas Weißschuh <thomas.weissschuh@...utronix.de>,
Willy Tarreau <w@....eu>, Andy Lutomirski <luto@...capital.net>,
Will Drewry <wad@...omium.org>, Mark Brown <broonie@...nel.org>,
Muhammad Usama Anjum <usama.anjum@...labora.com>,
linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org,
Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH v4 00/14] kselftest harness and nolibc compatibility
On 5/10/25 00:54, Thomas Weißschuh wrote:
> Hi Shuah and Kees,
>
> On 2025-05-05 17:15:18+0200, Thomas Weißschuh wrote:
>> Nolibc is useful for selftests as the test programs can be very small,
>> and compiled with just a kernel crosscompiler, without userspace support.
>> Currently nolibc is only usable with kselftest.h, not the more
>> convenient to use kselftest_harness.h
>> This series provides this compatibility by removing the usage of problematic
>> libc features from the harness.
>
> I'd like to get this series into the next merge window.
> For that I'd like to expose it to linux-next through the nolibc tree.
> If you don't have the time for a review or issues crop up, I will drop
> the patches again.
>
> Are you fine with that?
Didn't I respond to v13 saying you can include in your nolibc PR?
If I didn't here is my Reviewed-by.
>
> The issues reported by Mark have been fixed and tests have been written
> for them.
Reviewed-by: Shuah Khan <skhan@...uxfoundation.org>
thanks,
-- Shuah
Powered by blists - more mailing lists