public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Nicolas Schier" <nsc@kernel.org>,
	"Brian Cain" <bcain@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Arnd Bergmann" <arnd@arndb.de>,
	linux-hexagon@vger.kernel.org,
	"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: Re: [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers
Date: Mon, 9 Mar 2026 18:00:21 -0700	[thread overview]
Message-ID: <20260310010021.GA1321389@ax162> (raw)
In-Reply-To: <20260227-kbuild-uapi-libc-v1-0-c17de0d19776@weissschuh.net>

On Fri, Feb 27, 2026 at 07:37:58AM +0100, Thomas Weißschuh wrote:
> Currently the test compilation of some UAPI headers requires a toolchain
> libc headers. Remove that dependency.
> 
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Thomas Weißschuh (9):
>       hexagon: uapi: Fix structure alignment attribute
>       kbuild: uapi: test linux/bpf_perf_event.h on powerpc
>       kbuild: uapi: deduplicate linux/bpf_perf_event.h exclusions
>       kbuild: uapi: completely exclude linux/bpf_perf_event.h on nios2
>       kbuild: uapi: only use dummy-include for headers which use libc
>       kbuild: uapi: provide stub includes for some libc headers
>       kbuild: uapi: use custom stub headers instead of libc ones
>       kbuild: uapi: simplify libc dependency logic
>       kbuild: uapi: remove now unneeded guard headers

This is nice! For the series:

Reviewed-by: Nathan Chancellor <nathan@kernel.org>

Cheers,
Nathan

  parent reply	other threads:[~2026-03-10  1:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  6:37 [PATCH 0/9] kbuild: uapi: remove usage of toolchain headers 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
2026-03-05  9:41 ` Nicolas Schier
2026-03-10  1:00 ` Nathan Chancellor [this message]
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=20260310010021.GA1321389@ax162 \
    --to=nathan@kernel.org \
    --cc=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=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