linux-kernel - Re: [PATCH 0/5] kbuild: uapi: improvements to header testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176773745004.1983625.3214132191933293574.b4-ty@kernel.org>
Date: Tue, 06 Jan 2026 15:10:50 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nsc@...nel.org>, 
 Brian Cain <bcain@...nel.org>, 
 Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Cc: linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org, 
 bpf@...r.kernel.org, linux-hexagon@...r.kernel.org
Subject: Re: [PATCH 0/5] kbuild: uapi: improvements to header testing

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@...nel.org>