All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Nicolas Schier <nsc@kernel.org>, Brian Cain <bcain@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	bpf@vger.kernel.org, linux-hexagon@vger.kernel.org
Subject: Re: [PATCH 0/5] kbuild: uapi: improvements to header testing
Date: Tue, 30 Dec 2025 13:31:56 -0700	[thread overview]
Message-ID: <20251230203156.GD4062669@ax162> (raw)
In-Reply-To: <20251223-uapi-nostdinc-v1-0-d91545d794f7@linutronix.de>

Hi Thomas,

On Tue, Dec 23, 2025 at 08:04:07AM +0100, Thomas Weißschuh wrote:
> Also validate that UAPI headers do not depend on libc and remove the
> dependency on CC_CAN_LINK.
> 
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> Thomas Weißschuh (5):
>       kbuild: uapi: validate that headers do not use libc
>       hexagon: Drop invalid UAPI header asm/signal.h
>       kbuild: uapi: don't compile test bpf_perf_event.h on xtensa
>       kbuild: uapi: split out command conditions into variables
>       kbuild: uapi: drop dependency on CC_CAN_LINK
> 
>  arch/hexagon/include/{uapi => }/asm/signal.h |  0
>  init/Kconfig                                 |  2 +-
>  usr/include/Makefile                         | 87 +++++++++++++++++++++++++++-
>  3 files changed, 87 insertions(+), 2 deletions(-)

This seems like a great improvement to the UAPI header testing. I don't
see any immediate problems and it works for me in my brief local
testing. I will give a week or so for comments before I apply this to
kbuild-next (plus -next should be operating at that point).

Cheers,
Nathan

  parent reply	other threads:[~2025-12-30 20:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-23  7:04 [PATCH 0/5] kbuild: uapi: improvements to header testing Thomas Weißschuh
2025-12-23  7:04 ` [PATCH 1/5] kbuild: uapi: validate that headers do not use libc Thomas Weißschuh
2025-12-23  7:04 ` [PATCH 2/5] hexagon: Drop invalid UAPI header asm/signal.h Thomas Weißschuh
2025-12-23  7:04 ` [PATCH 3/5] kbuild: uapi: don't compile test bpf_perf_event.h on xtensa Thomas Weißschuh
2025-12-23  7:04 ` [PATCH 4/5] kbuild: uapi: split out command conditions into variables Thomas Weißschuh
2025-12-23  7:04 ` [PATCH 5/5] kbuild: uapi: drop dependency on CC_CAN_LINK Thomas Weißschuh
2025-12-30 20:31 ` Nathan Chancellor [this message]
2026-01-06 22:10 ` [PATCH 0/5] kbuild: uapi: improvements to header testing Nathan Chancellor

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=20251230203156.GD4062669@ax162 \
    --to=nathan@kernel.org \
    --cc=bcain@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.