From: "Paul E. McKenney" <paulmck@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: linux@weissschuh.net, v@vda.io, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tools/nolibc: assorted build fixes for nolibc-test in rare cases
Date: Sun, 2 Apr 2023 10:13:32 -0700 [thread overview]
Message-ID: <369c34e4-3ed0-44fe-817f-e724a02bdb02@paulmck-laptop> (raw)
In-Reply-To: <20230402081357.12078-1-w@1wt.eu>
On Sun, Apr 02, 2023 at 10:13:55AM +0200, Willy Tarreau wrote:
> Hello Paul,
>
> please find in this series two small build fixes. One of them concerns
> two missing include files for building the test against other libc (at
> least glibc) since we added the tests for integer types and ranges. The
> second one removes a single occurrence of a variable definition inside
> the init statement of a for loop that breaks with older compilers which
> do not default to c99. They're still convenient to test the portability
> of the lib itself and I continue to use them for this purpose.
>
> I consider that there's no rush on this, since these issues only affect
> developers adding test cases, who should normally rebase on top of your
> dev branch. So it's fine if it goes there.
Queued and pushed for the v6.5 merge window (the one after the upcoming
one), thank you!
Thanx, Paul
> Thank you!
> Willy
>
> Willy Tarreau (2):
> tools/nolibc: tests: fix build on non-c99 compliant compilers
> tools/nolibc: fix build of the test case using glibc
>
> tools/testing/selftests/nolibc/nolibc-test.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> --
> 2.17.5
>
prev parent reply other threads:[~2023-04-02 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 8:13 Willy Tarreau
2023-04-02 8:13 ` [PATCH 1/2] tools/nolibc: tests: fix build on non-c99 compliant compilers Willy Tarreau
2023-04-02 8:13 ` [PATCH 2/2] tools/nolibc: fix build of the test case using glibc Willy Tarreau
2023-04-02 17:13 ` Paul E. McKenney [this message]
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=369c34e4-3ed0-44fe-817f-e724a02bdb02@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=v@vda.io \
--cc=w@1wt.eu \
/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®