From: Nathan Chancellor <nathan@kernel.org>
To: Nicolas Schier <nsc@kernel.org>
Cc: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] kbuild: uapi: upgrade check_sizetypes() warning to error
Date: Thu, 9 Oct 2025 09:56:18 -0700 [thread overview]
Message-ID: <20251009165618.GA441460@ax162> (raw)
In-Reply-To: <aObA4vNF4tppZ5vR@levanger>
On Wed, Oct 08, 2025 at 09:52:02PM +0200, Nicolas Schier wrote:
> Good question. I think you're right, that header compiling should be
> enough.
>
> I cannot think of a sensible way that with successful header compile
> test for an UAPI header file that is not contained.
>
> Setting USERCFLAGS='-include something/like/types.h' during header
> compilation may hide a missing '#include <linux/types.h>', but I don't
> think that this is a good reason to keep the checking.
Yeah that seems extremely unlikely to me...
Okay, I think I will send Geert's fix for 6.18 then send a patch in a
couple of weeks that removes this check from headers_check.pl
altogether for 6.19.
Cheers,
Nathan
next prev parent reply other threads:[~2025-10-09 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 6:16 [PATCH v2 0/5] kbuild: uapi: various fixes Thomas Weißschuh
2025-08-13 6:16 ` [PATCH v2 1/5] kbuild: uapi: rerun header tests when headers_check.pl changes Thomas Weißschuh
2025-08-13 6:16 ` [PATCH v2 2/5] kbuild: uapi: fail header test on compiler warnings Thomas Weißschuh
2025-08-13 6:16 ` [PATCH v2 3/5] kbuild: uapi: upgrade warning on asm/types.h inclusion to error Thomas Weißschuh
2025-08-13 6:16 ` [PATCH v2 4/5] kbuild: uapi: upgrade check_sizetypes() warning " Thomas Weißschuh
2025-10-06 8:53 ` Geert Uytterhoeven
2025-10-06 19:00 ` Nathan Chancellor
2025-10-08 19:52 ` Nicolas Schier
2025-10-09 16:56 ` Nathan Chancellor [this message]
2025-08-13 6:17 ` [PATCH v2 5/5] kbuild: uapi: upgrade check_declarations() " Thomas Weißschuh
2025-08-14 19:11 ` [PATCH v2 0/5] kbuild: uapi: various fixes 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=20251009165618.GA441460@ax162 \
--to=nathan@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