From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Willy Tarreau <w@1wt.eu>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kernel@vger.kernel.org,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [RFC PATCH 1/3] tools/nolibc: merge i386 and x86_64 into a single x86 arch
Date: Sat, 21 Jun 2025 10:29:41 +0200 [thread overview]
Message-ID: <d577e0ed-0cdd-4fe9-a678-9669993ee9f7@t-8ch.de> (raw)
In-Reply-To: <20250620103705.10208-2-w@1wt.eu>
On 2025-06-20 12:37:03+0200, Willy Tarreau wrote:
> This remained the only exception to the kernel's architectures
> organization and it's always a bit cumbersome to deal with. Let's merge
> i386 and x86_64 into x86. This will result in a single arch-x86.h file
> by default, and we'll no longer need to merge the two manually during
> installation. Requesting either i386 or x86_64 will also result in
> installing x86.
We should do this in any case, independently from the series.
Acked-by: Thomas Weißschuh <linux@weissschuh.net>
> Signed-off-by: Willy Tarreau <w@1wt.eu>
> ---
> tools/include/nolibc/Makefile | 10 +-
> tools/include/nolibc/arch-i386.h | 178 -----------------
> .../nolibc/{arch-x86_64.h => arch-x86.h} | 180 +++++++++++++++++-
> tools/include/nolibc/arch.h | 6 +-
> 4 files changed, 179 insertions(+), 195 deletions(-)
> delete mode 100644 tools/include/nolibc/arch-i386.h
> rename tools/include/nolibc/{arch-x86_64.h => arch-x86.h} (53%)
<snip>
next prev parent reply other threads:[~2025-06-21 8:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:37 [RFC PATCH 0/3] tools/nolibc: install unified multi-arch headers Willy Tarreau
2025-06-20 10:37 ` [RFC PATCH 1/3] tools/nolibc: merge i386 and x86_64 into a single x86 arch Willy Tarreau
2025-06-21 8:29 ` Thomas Weißschuh [this message]
2025-06-21 8:44 ` Willy Tarreau
2025-06-20 10:37 ` [RFC PATCH 2/3] tools/nolibc: add a new target "headers_all_archs" to loop over all archs Willy Tarreau
2025-06-23 21:56 ` Thomas Weißschuh
2025-06-24 6:20 ` Willy Tarreau
2025-06-24 7:46 ` Thomas Weißschuh
2025-06-24 10:00 ` Willy Tarreau
2025-06-20 10:37 ` [RFC PATCH 3/3] tools/nolibc: add a new "install_all_archs" target Willy Tarreau
2025-06-26 20:18 ` Thomas Weißschuh
2025-06-26 21:15 ` Arnd Bergmann
2025-06-27 3:25 ` Willy Tarreau
2025-06-27 5:58 ` Arnd Bergmann
2025-06-27 6:07 ` Willy Tarreau
2025-06-27 5:11 ` Thomas Weißschuh
2025-06-27 5:46 ` Willy Tarreau
2025-06-27 5:49 ` Willy Tarreau
2025-06-27 7:27 ` Thomas Weißschuh
2025-06-27 7:29 ` 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=d577e0ed-0cdd-4fe9-a678-9669993ee9f7@t-8ch.de \
--to=linux@weissschuh.net \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--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®