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: Tue, 7 Feb 2023 04:21:14 +0100 [thread overview]
Message-ID: <Y+HDqlMR6QndYSN4@1wt.eu> (raw)
In-Reply-To: <bff2a9f8-6f70-409a-8acb-cf8917f653a6@app.fastmail.com>
On Mon, Feb 06, 2023 at 05:19:18PM -0500, Vincent Dagonneau wrote:
> > - do not forget your signed-off-by on patches.
> >
>
> Again, sorry. I'm quite new to the send-email workflow. I just figured that I
> was probably supposed to use format-patch then send-email rather than just
> send-email... Makes way more sense though and now I can have a file with my
> cover letter and carry it over to the next version.
Don't be sorry. It can take a bit of time to get used to send-email (and
can be scary at times). And yes, I, too, prefer to first produce the
patches then send them. One advice is to produce them into a different
directory each time, it will save you from accidently sending a mix of
the previous version and the current one, and it will also help you
double-check the differences between the patches to see check if you
missed anything.
> >> 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!
> >
>
> Ah, foolishly I was relying on the packaged cross compiler for Arch. Compiled
> everything just fine with the packaged versions on Ubuntu (gcc-10
> mips/arm/arm64/i386). I'll try with the toolchains @
> https://mirrors.edge.kernel.org/pub/tools/crosstool/ as well.
OK!
Cheers,
Willy
prev parent reply other threads:[~2023-02-07 3:21 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 ` [PATCH v3 0/4] tools/nolibc: Adding stdint.h, more integer types and tests Willy Tarreau
2023-02-06 22:19 ` Vincent Dagonneau
2023-02-07 3:21 ` Willy Tarreau [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=Y+HDqlMR6QndYSN4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox