linux-kernel - Re: [PATCH v3 0/4] tools/nolibc: Adding stdint.h, more integer types and tests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y+HDqlMR6QndYSN4@1wt.eu>
Date:   Tue, 7 Feb 2023 04:21:14 +0100
From:   Willy Tarreau <w@....eu>
To:     Vincent Dagonneau <v@....io>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] tools/nolibc: Adding stdint.h, more integer types
 and tests

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