From: Nathan Chancellor <nathan@kernel.org>
To: "Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>,
"Brian Cain" <bcain@kernel.org>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: 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, 06 Jan 2026 15:10:50 -0700 [thread overview]
Message-ID: <176773745004.1983625.3214132191933293574.b4-ty@kernel.org> (raw)
In-Reply-To: <20251223-uapi-nostdinc-v1-0-d91545d794f7@linutronix.de>
On Tue, 23 Dec 2025 08:04:07 +0100, Thomas Weißschuh wrote:
> Also validate that UAPI headers do not depend on libc and remove the
> dependency on CC_CAN_LINK.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next-unstable
Thanks!
[1/5] kbuild: uapi: validate that headers do not use libc
https://git.kernel.org/kbuild/c/6059b880a93c3
[2/5] hexagon: Drop invalid UAPI header asm/signal.h
https://git.kernel.org/kbuild/c/cc45d2ea5cfb8
[3/5] kbuild: uapi: don't compile test bpf_perf_event.h on xtensa
https://git.kernel.org/kbuild/c/e2772ba5f43df
[4/5] kbuild: uapi: split out command conditions into variables
https://git.kernel.org/kbuild/c/4ac85d9bc73ed
[5/5] kbuild: uapi: drop dependency on CC_CAN_LINK
https://git.kernel.org/kbuild/c/e3970d77ec504
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
prev parent reply other threads:[~2026-01-06 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 7:04 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 ` [PATCH 0/5] kbuild: uapi: improvements to header testing Nathan Chancellor
2026-01-06 22:10 ` Nathan Chancellor [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=176773745004.1983625.3214132191933293574.b4-ty@kernel.org \
--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 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®