From: Willy Tarreau <w@1wt.eu>
To: Vincent Dagonneau <v@vda.io>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] tools/nolibc: Adding stdint.h, more integer types and tests
Date: Mon, 6 Feb 2023 09:30:18 +0100 [thread overview]
Message-ID: <Y+C6mj4F77U43atS@1wt.eu> (raw)
In-Reply-To: <20230206013248.471664-1-v@vda.io>
Hi Vincent,
On Sun, Feb 05, 2023 at 08:32:45PM -0500, Vincent Dagonneau wrote:
> Hi,
>
> This is version 3 of my patch to add stdint.h to nolibc. Previous
> versions of this patch are available here:
>
> * v2: https://lore.kernel.org/all/20230202201101.43160-1-v@vda.io/
> * v1: https://lore.kernel.org/all/20230202160236.25342-1-v@vda.io/
>
> This version should address most of the concerns raised by Willy on the
> previous version (missing LL, ULL suffixes, uintptr/size_max size).
OK thank you, that's much better already. I'm still having a few comments:
- please avoid the present participle in the subjects of your commits,
the imperative form is generally preferred (e.g: "add foo" instead of
"adding foo").
- do not forget your signed-off-by on patches.
- 3rd commit had an empty message. There's always something to say
about a change, at least why and what it provides.
- You still have this definition which is only valid for 64-bit,
you will need to move it to your ifdef __WORDSIZE block to adjust
it based on the word size:
#define SIZE_MAX UINT64_MAX
Maybe this one should also be part of the tests ?
> I tested it successfully on x86_64 and arm64 (on qemu). I have some
> trouble setting up my cross compilation chain for i386, arm and mips
> however.
What compilers do you use ? I'm using version 11.3 from these ones:
https://mirrors.edge.kernel.org/pub/tools/crosstool/
All supported archs work fine for me. Usually on x86_64 you can even
start the i386 binaries locally (if your kernel has COMPAT or COMPAT_32
built in, which is most often the case). And very commonly arm64 support
armv7 binaries as well.
Just let me know if I can help you set up your environment, it's always
a good long-term investment!
Regards,
Willy
next prev parent reply other threads:[~2023-02-06 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 1:32 [PATCH v3 0/4] tools/nolibc: Adding stdint.h, more integer types and tests Vincent Dagonneau
2023-02-06 1:32 ` [PATCH v3 1/4] tools/nolibc: Adding stdint.h Vincent Dagonneau
2023-02-06 1:32 ` [PATCH v3 2/4] tools/nolibc: Adding integer types and integer limit macros Vincent Dagonneau
2023-02-06 1:32 ` [PATCH v3 3/4] tools/nolibc: Enlarging column width of tests Vincent Dagonneau
2023-02-06 1:32 ` [PATCH v3 4/4] tools/nolibc: Adding tests for the integer limits in stdint.h Vincent Dagonneau
2023-02-06 8:30 ` Willy Tarreau [this message]
2023-02-06 22:19 ` [PATCH v3 0/4] tools/nolibc: Adding stdint.h, more integer types and tests Vincent Dagonneau
2023-02-07 3:21 ` 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=Y+C6mj4F77U43atS@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.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.