From: Nathan Chancellor <nathan@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Nicolas Schier <nicolas.schier@linux.dev>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: uapi: reuse KBUILD_USERCFLAGS
Date: Tue, 14 Oct 2025 17:19:21 -0700 [thread overview]
Message-ID: <20251015001921.GA2263607@ax162> (raw)
In-Reply-To: <20251014-kbuild-uapi-usercflags-v1-1-c162f9059c47@linutronix.de>
On Tue, Oct 14, 2025 at 07:55:32AM +0200, Thomas Weißschuh wrote:
> The toplevel Makefile already provides the compiler flags necessary to
> build userspace applications for the target.
>
> Make use of them instead of duplicating the logic.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
Seems reasonable to me.
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> usr/include/Makefile | 11 ++---------
> 1 file changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/usr/include/Makefile b/usr/include/Makefile
> index 61a7dd4fc05f004d785c64c0019ad846c84719d5..d8a508042fed315401ed689e0839af249c4b31c8 100644
> --- a/usr/include/Makefile
> +++ b/usr/include/Makefile
> @@ -6,16 +6,9 @@
> #
> # -std=c90 (equivalent to -ansi) catches the violation of those.
> # We cannot go as far as adding -Wpedantic since it emits too many warnings.
> -UAPI_CFLAGS := -std=c90 -Wall -Werror=implicit-function-declaration
> +UAPI_CFLAGS := -std=c90 -Werror=implicit-function-declaration
>
> -# In theory, we do not care -m32 or -m64 for header compile tests.
> -# It is here just because CONFIG_CC_CAN_LINK is tested with -m32 or -m64.
> -UAPI_CFLAGS += $(filter -m32 -m64 --target=%, $(KBUILD_CPPFLAGS) $(KBUILD_CFLAGS))
> -
> -# USERCFLAGS might contain sysroot location for CC.
> -UAPI_CFLAGS += $(USERCFLAGS)
> -
> -override c_flags = $(UAPI_CFLAGS) -Wp,-MMD,$(depfile) -I $(obj) -I $(srctree)/usr/dummy-include
> +override c_flags = $(KBUILD_USERCFLAGS) $(UAPI_CFLAGS) -Wp,-MMD,$(depfile) -I $(obj) -I $(srctree)/usr/dummy-include
>
> # The following are excluded for now because they fail to build.
> #
>
> ---
> base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
> change-id: 20251013-kbuild-uapi-usercflags-affb222af087
>
> Best regards,
> --
> Thomas Weißschuh <thomas.weissschuh@linutronix.de>
>
next prev parent reply other threads:[~2025-10-15 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 5:55 [PATCH] kbuild: uapi: reuse KBUILD_USERCFLAGS Thomas Weißschuh
2025-10-15 0:19 ` Nathan Chancellor [this message]
2025-10-22 21:20 ` 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=20251015001921.GA2263607@ax162 \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.schier@linux.dev \
--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