From: Shuah Khan <skhan@linuxfoundation.org>
To: "Willy Tarreau" <w@1wt.eu>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Kees Cook" <kees@kernel.org>
Cc: "Shuah Khan" <shuah@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>,
"Andy Lutomirski" <luto@amacapital.net>,
"Will Drewry" <wad@chromium.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 00/32] kselftest harness and nolibc compatibility
Date: Thu, 24 Apr 2025 14:06:34 -0600 [thread overview]
Message-ID: <7bb64160-103c-4882-a69b-9bc054e62db8@linuxfoundation.org> (raw)
In-Reply-To: <20250422085145.GB14589@1wt.eu>
On 4/22/25 02:51, Willy Tarreau wrote:
> Hi Thomas,
>
> On Tue, Apr 22, 2025 at 10:48:28AM +0200, Thomas Weißschuh wrote:
>> Hi,
>>
>> On Fri, Apr 11, 2025 at 11:00:24AM +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 adding new features to nolibc
>>> and removing the usage of problematic features from the harness.
>>>
>>> The first half of the series are changes to the harness, the second one
>>> are for nolibc. Both parts are very independent and should go through
>>> different trees.
>>
>> I need a few nolibc bits of this series (snprintf() and prep patches) to base
>> further patches on. For that I'd like to pick up all the nolibc patches from
>> this series through the nolibc tree. They got Acks from Willy.
>>
>> Any objections?
>
> No objection on my side!
>
Thanks.
Kees, do you have any comments on this series? If you are okay
with it, I would like to apply this for next.
thanks,
-- Shuah
next prev parent reply other threads:[~2025-04-24 20:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 9:00 [PATCH v3 00/32] kselftest harness and nolibc compatibility Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 01/32] selftests: harness: Add kselftest harness selftest Thomas Weißschuh
2025-04-18 16:56 ` Muhammad Usama Anjum
2025-04-11 9:00 ` [PATCH v3 02/32] selftests: harness: Use C89 comment style Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 03/32] selftests: harness: Ignore unused variant argument warning Thomas Weißschuh
2025-04-18 16:57 ` Muhammad Usama Anjum
2025-04-11 9:00 ` [PATCH v3 04/32] selftests: harness: Mark functions without prototypes static Thomas Weißschuh
2025-04-18 16:59 ` Muhammad Usama Anjum
2025-04-11 9:00 ` [PATCH v3 05/32] selftests: harness: Remove inline qualifier for wrappers Thomas Weißschuh
2025-04-18 17:00 ` Muhammad Usama Anjum
2025-04-11 9:00 ` [PATCH v3 06/32] selftests: harness: Remove dependency on libatomic Thomas Weißschuh
2025-04-18 17:16 ` Muhammad Usama Anjum
2025-04-11 9:00 ` [PATCH v3 07/32] selftests: harness: Implement test timeouts through pidfd Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 08/32] selftests: harness: Don't set setup_completed for fixtureless tests Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 09/32] selftests: harness: Always provide "self" and "variant" Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 10/32] selftests: harness: Move teardown conditional into test metadata Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 11/32] selftests: harness: Add teardown callback to " Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 12/32] selftests: harness: Stop using setjmp()/longjmp() Thomas Weißschuh
2025-05-05 10:50 ` Mark Brown
2025-05-05 14:07 ` Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 13/32] selftests: harness: Guard includes on nolibc Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 14/32] tools/nolibc: handle intmax_t/uintmax_t in printf Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 15/32] tools/nolibc: use intmax definitions from compiler Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 16/32] tools/nolibc: use pselect6_time64 if available Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 17/32] tools/nolibc: use ppoll_time64 " Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 18/32] tools/nolibc: add tolower() and toupper() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 19/32] tools/nolibc: add _exit() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 20/32] tools/nolibc: add setpgrp() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 21/32] tools/nolibc: implement waitpid() in terms of waitid() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 22/32] Revert "selftests/nolibc: use waitid() over waitpid()" Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 23/32] tools/nolibc: add dprintf() and vdprintf() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 24/32] tools/nolibc: add getopt() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 25/32] tools/nolibc: allow different write callbacks in printf Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 26/32] tools/nolibc: allow limiting of printf destination size Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 27/32] tools/nolibc: add snprintf() and friends Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 28/32] selftests/nolibc: use snprintf() for printf tests Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 29/32] selftests/nolibc: rename vfprintf test suite Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 30/32] selftests/nolibc: add test for snprintf() truncation Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 31/32] tools/nolibc: implement width padding in printf() Thomas Weißschuh
2025-04-11 9:00 ` [PATCH v3 32/32] HACK: selftests/nolibc: demonstrate usage of the kselftest harness Thomas Weißschuh
2025-04-22 8:48 ` [PATCH v3 00/32] kselftest harness and nolibc compatibility Thomas Weißschuh
2025-04-22 8:51 ` Willy Tarreau
2025-04-24 20:06 ` Shuah Khan [this message]
2025-04-29 18:52 ` Shuah Khan
2025-04-29 19:25 ` Thomas Weißschuh
2025-04-30 18:53 ` Kees Cook
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=7bb64160-103c-4882-a69b-9bc054e62db8@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=luto@amacapital.net \
--cc=shuah@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=w@1wt.eu \
--cc=wad@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.