From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: use arm64 name over aarch64
Date: Tue, 24 Jun 2025 08:14:57 +0200 [thread overview]
Message-ID: <20250624061457.GC30919@1wt.eu> (raw)
In-Reply-To: <20250623-nolibc-aarch64-arm64-v1-1-a2892f1c1b27@weissschuh.net>
On Mon, Jun 23, 2025 at 11:48:34PM +0200, Thomas Weißschuh wrote:
> Nolibc generally uses the kernel's architecture names.
> aarch64 is the only exception.
>
> Remove the special case.
> Nothing changes for the users.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
I have been hesitating to do the same as well but remained
undecided. The fact that you thought the same confirms that
it's better this way.
Acked-by: Willy Tarreau <w@1wt.eu>
Thanks!
Willy
prev parent reply other threads:[~2025-06-24 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 21:48 Thomas Weißschuh
2025-06-24 6:14 ` 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=20250624061457.GC30919@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
/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®