mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nsc@kernel.org>,
	"Brian Cain" <bcain@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-hexagon@vger.kernel.org
Subject: Re: [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers
Date: Fri, 27 Feb 2026 11:04:51 +0100	[thread overview]
Message-ID: <eddd2b82-6ad2-4345-82fd-21606fa7d245@app.fastmail.com> (raw)
In-Reply-To: <20260227103449-a526a376-153c-4f86-bfc9-2eddbdde58fd@linutronix.de>

On Fri, Feb 27, 2026, at 10:38, Thomas Weißschuh wrote:
> On Fri, Feb 27, 2026 at 10:18:41AM +0100, Arnd Bergmann wrote:
>> On Fri, Feb 27, 2026, at 07:37, Thomas Weißschuh wrote:
>> 
>> I had toyed around with a similar series, using a slightly different
>> approach of always using the in-kernel nolibc headers, and making
>> those compile across all architectures (using empty stubs for those
>> that are missing syscall entry functions).
>> 
>> I don't care much which way we do this as long as we can build test
>> the headers, but I wonder what your reason was for picking this
>> approach over the other.
>
> My goal is to reduce the reliance of the UAPI headers on libc ones.
> Hopefully we can remove libc usages from the UAPI headers and then also
> drop the compatibility bits from the stub headers. If we use the full nolibc
> the message to UAPI authors would not be clear and new dependencies may be
> introduced again.

Good point, thanks for the clarification!

      Arnd

  reply	other threads:[~2026-02-27 10:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:37 Thomas Weißschuh
2026-02-27  6:37 ` [PATCH 1/9] hexagon: uapi: Fix structure alignment attribute Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 2/9] kbuild: uapi: test linux/bpf_perf_event.h on powerpc Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 3/9] kbuild: uapi: deduplicate linux/bpf_perf_event.h exclusions Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 4/9] kbuild: uapi: completely exclude linux/bpf_perf_event.h on nios2 Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 5/9] kbuild: uapi: only use dummy-include for headers which use libc Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 6/9] kbuild: uapi: provide stub includes for some libc headers Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 7/9] kbuild: uapi: use custom stub headers instead of libc ones Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 8/9] kbuild: uapi: simplify libc dependency logic Thomas Weißschuh
2026-02-27  6:38 ` [PATCH 9/9] kbuild: uapi: remove now unneeded guard headers Thomas Weißschuh
2026-02-27  9:18 ` [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers Arnd Bergmann
2026-02-27  9:38   ` Thomas Weißschuh
2026-02-27 10:04     ` Arnd Bergmann [this message]
2026-03-05  9:41 ` Nicolas Schier
2026-03-10  1:00 ` Nathan Chancellor
2026-03-12 12:08 ` Nicolas Schier

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=eddd2b82-6ad2-4345-82fd-21606fa7d245@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=bcain@kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=thomas.weissschuh@linutronix.de \
    /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®