From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux@weissschuh.net, linux-kernel@vger.kernel.org,
Vincent Dagonneau <v@vda.io>
Subject: Re: [PATCH 1/4] tools/nolibc: add stdint.h
Date: Sun, 5 Mar 2023 05:27:29 +0100 [thread overview]
Message-ID: <ZAQaMTNqPo55OA8X@1wt.eu> (raw)
In-Reply-To: <20230305004734.GA1270367@paulmck-ThinkPad-P17-Gen-1>
Hello Paul,
On Sat, Mar 04, 2023 at 04:47:34PM -0800, Paul E. McKenney wrote:
> On Sat, Mar 04, 2023 at 03:26:03PM +0100, Willy Tarreau wrote:
> > From: Vincent Dagonneau <v@vda.io>
> >
> > Nolibc works fine for small and limited program however most program
> > expect integer types to be defined in stdint.h rather than std.h.
> >
> > This is a quick fix that moves the existing integer definitions in std.h
> > to stdint.h.
> >
> > Signed-off-by: Vincent Dagonneau <v@vda.io>
> > Reviewed-by: Thomas Weißschuh <linux@weissschuh.net>
> > Signed-off-by: Willy Tarreau <w@1wt.eu>
>
> I queued all three serieses, and it does look good, thank you!
>
> make[1]: Leaving directory '/home/git/linux-rcu'
> 125 test(s) passed.
>
> I am figuring on pushing these into the v6.4 merge window, that is,
> the one after the current just-now-closing merge window.
Yes that was the intent, so that we still have time to make some
adjustments if any would be needed. Many thanks!
Willy
next prev parent reply other threads:[~2023-03-05 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 14:26 [PATCH 0/4] tools/nolibc: add stdint and more integer types Willy Tarreau
2023-03-04 14:26 ` [PATCH 1/4] tools/nolibc: add stdint.h Willy Tarreau
2023-03-05 0:47 ` Paul E. McKenney
2023-03-05 4:27 ` Willy Tarreau [this message]
2023-03-04 14:26 ` [PATCH 2/4] tools/nolibc: add integer types and integer limit macros Willy Tarreau
2023-03-04 14:26 ` [PATCH 3/4] tools/nolibc: enlarge column width of tests Willy Tarreau
2023-03-04 14:26 ` [PATCH 4/4] tools/nolibc: add tests for the integer limits in stdint.h 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=ZAQaMTNqPo55OA8X@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=paulmck@kernel.org \
--cc=v@vda.io \
/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.