From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Willy Tarreau <w@1wt.eu>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kernel@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [RFC PATCH v2 2/2] tools/nolibc: add a new "install_all_archs" target
Date: Mon, 7 Jul 2025 17:41:56 +0200 [thread overview]
Message-ID: <85c93c7c-239c-47aa-8a4e-d944c828314b@t-8ch.de> (raw)
In-Reply-To: <20250706070124.GD29601@1wt.eu>
On 2025-07-06 09:01:24+0200, Willy Tarreau wrote:
<snip>
> If it is made clear that there is no interest in packaging uapi headers
> for archs not supported by nolibc, then this means that nolibc can be
> the place where the archs to be packaged is decided, and the two can
> be more tightly coupled, but as of now, this lack of interest is not
> yet obvious to me.
Given that this functionality was removed from kbuild recently I assume
that it there is limited interest to get it back.
Also in v2 none of the kbuild maintainers or list are Cc-ed anymore.
IMO we can apply patch 1 first and on its own.
Thomas
prev parent reply other threads:[~2025-07-07 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 17:07 [RFC PATCH v2 0/2] tools/nolibc: install unified multi-arch headers Willy Tarreau
2025-06-29 17:07 ` [RFC PATCH v2 1/2] tools/nolibc: make the "headers" target install all supported archs Willy Tarreau
2025-06-29 20:17 ` Thomas Weißschuh
2025-06-29 17:07 ` [RFC PATCH v2 2/2] tools/nolibc: add a new "install_all_archs" target Willy Tarreau
2025-06-29 20:44 ` Thomas Weißschuh
2025-07-06 7:01 ` Willy Tarreau
2025-07-07 15:41 ` Thomas Weißschuh [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=85c93c7c-239c-47aa-8a4e-d944c828314b@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.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®