All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 1/4] tools/nolibc: add libc-test binary
Date: Sun, 2 Apr 2023 20:37:13 +0200	[thread overview]
Message-ID: <ZCnLWQ2BCisgmP+a@1wt.eu> (raw)
In-Reply-To: <20230328-nolibc-printf-test-v3-1-ddc79f92efd5@weissschuh.net>

On Sun, Apr 02, 2023 at 06:04:34PM +0000, Thomas Weißschuh wrote:
> This can be used to easily compare the behavior of nolibc to the system
> libc.
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> 
> ---
> 
> Feel free to drop this if it does not fit in.

On the opposite! I wanted to do it, you beat me to it. I'm just going to
add an entry for it in the help message.

Thank you!
Willy

  reply	other threads:[~2023-04-02 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-02 18:04 [PATCH v3 0/4] tools/nolibc: add testcases for vfprintf Thomas Weißschuh
2023-04-02 18:04 ` [PATCH v3 1/4] tools/nolibc: add libc-test binary Thomas Weißschuh
2023-04-02 18:37   ` Willy Tarreau [this message]
2023-04-02 18:04 ` [PATCH v3 2/4] tools/nolibc: add wrapper for memfd_create Thomas Weißschuh
2023-04-02 18:04 ` [PATCH v3 3/4] tools/nolibc: implement fd-based FILE streams Thomas Weißschuh
2023-04-12 15:58   ` Mark Brown
2023-04-12 15:58     ` Mark Brown
2023-04-13 13:09     ` linux
2023-04-13 13:09       ` linux
2023-04-13 14:20       ` Mark Brown
2023-04-13 14:20         ` Mark Brown
2023-04-02 18:04 ` [PATCH v3 4/4] tools/nolibc: add testcases for vfprintf Thomas Weißschuh
2023-04-02 18:49 ` [PATCH v3 0/4] " Willy Tarreau

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=ZCnLWQ2BCisgmP+a@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=shuah@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 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.