mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ammar Faizi <ammarfaizi2@gnuweeb.org>
Subject: Re: [PATCH 0/8] nolibc: small updates required for the self-tests
Date: Mon, 21 Mar 2022 21:33:19 +0100	[thread overview]
Message-ID: <20220321203319.GA8066@1wt.eu> (raw)
In-Reply-To: <20220321202908.GI4285@paulmck-ThinkPad-P17-Gen-1>

On Mon, Mar 21, 2022 at 01:29:08PM -0700, Paul E. McKenney wrote:
> On Mon, Mar 21, 2022 at 06:33:06PM +0100, Willy Tarreau wrote:
> > Hello Paul,
> > 
> > while developing the nolibc self-tests, I naturally faced a few
> > limitations ranging from missing POLL* flags to missing strcmp() or
> > getenv(), as well as the ability for printf() to print "(null)" on
> > "%s" instead of crashing.
> > 
> > This series adds a makefile and a headers installation target that
> > creates a sysroot made of kernel headers and nolibc headers, which
> > significantly ease building programs.
> > 
> > I already have some test code with roughly 75 tests, but I find it
> > misplaced in the nolibc dir, I need to move it to testing/selftests/
> > before sending it to you.
> > 
> > This series is intended to be an add-on to what you already have in your
> > dev branch. I don't intend to send you much more stuff on top of this,
> > but I expect to see an update from Ammar's patch set (CCed). With all
> > this I think we'll have a good basis to easily add new tests.
> 
> I have pulled this series in for review and testing, thank you!
> 
> It won't go into -next until v5.18-rc1 comes out, in about two weeks,
> but it will at least be in -rcu.

Perfect, thank you!

> I removed an ostensibly extraneous blank line from the end of
> tools/include/nolibc/Makefile.  So please let me know if that blank line
> is actually necessary.

Oh I'm very sorry, that the type of thing I'm very careful about so it
has definitely escaped my checks.

Thanks,
Willy

  reply	other threads:[~2022-03-21 20:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 17:33 Willy Tarreau
2022-03-21 17:33 ` [PATCH 1/8] tools/nolibc/stdio: make printf(%s) accept NULL Willy Tarreau
2022-03-21 17:33 ` [PATCH 2/8] tools/nolibc/stdlib: add a simple getenv() implementation Willy Tarreau
2022-03-21 17:33 ` [PATCH 3/8] tools/nolibc/stdio: add support for '%p' to vfprintf() Willy Tarreau
2022-03-21 17:33 ` [PATCH 4/8] tools/nolibc/string: add strcmp() and strncmp() Willy Tarreau
2022-03-21 17:33 ` [PATCH 5/8] tools/nolibc/sys: add syscall definition for getppid() Willy Tarreau
2022-03-21 17:33 ` [PATCH 6/8] tools/nolibc/types: add poll() and waitpid() flag definitions Willy Tarreau
2022-03-21 17:33 ` [PATCH 7/8] tools/nolibc: add a makefile to install headers Willy Tarreau
2022-03-21 17:33 ` [PATCH 8/8] tools/nolibc: add the nolibc subdir to the common Makefile Willy Tarreau
2022-03-21 20:29 ` [PATCH 0/8] nolibc: small updates required for the self-tests Paul E. McKenney
2022-03-21 20:33   ` Willy Tarreau [this message]
2022-03-21 20:42     ` 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=20220321203319.GA8066@1wt.eu \
    --to=w@1wt.eu \
    --cc=ammarfaizi2@gnuweeb.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®