From: Nathan Chancellor <nathan@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.4 5/6] kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS
Date: Tue, 12 Aug 2025 14:11:45 -0700 [thread overview]
Message-ID: <20250812211145.GB532342@ax162> (raw)
In-Reply-To: <1754967622-c52851ba@stable.kernel.org>
Hi,
On Tue, Aug 12, 2025 at 12:12:25AM -0400, Sasha Levin wrote:
> > The upstream commit SHA1 provided is correct: feb843a469fb0ab00d2d23cfb9bcc379791011bb
>
> WARNING: Author mismatch between patch and upstream commit:
> Backport author: Nathan Chancellor <nathan@kernel.org>
> Commit author: Masahiro Yamada <masahiroy@kernel.org>
Hmmm, the patch has a "From:" header that has Masahiro as the author, is
that not sufficient for authorship?
> Status in newer kernel trees:
...
> 6.1.y | Not found
> 5.15.y | Not found
> 5.10.y | Not found
Odd, it appears to be there to me?
6.1.142: 8d21861f91a1 ("kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS")
5.15.186: 0690824cc325 ("kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS")
5.10.239: 951dfb0bdcd6 ("kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS")
> Found fixes commits:
> 02e9a22ceef0 kbuild: hdrcheck: fix cross build with clang
Unnecessary in 5.4: https://lore.kernel.org/20250617233200.GC3356351@ax162/
> 1b71c2fb04e7 kbuild: userprogs: fix bitsize and target detection on clang
Uncessary in 5.4: https://lore.kernel.org/20250617232006.GB3356351@ax162/
> 43fc0a99906e kbuild: Add KBUILD_CPPFLAGS to as-option invocation
43fc0a99906e is present in this series after feb843a469fb0a because that
is how it happened upstream but 43fc0a99906e could be applied before
feb843a469fb0a in stable.
Cheers,
Nathan
next prev parent reply other threads:[~2025-08-12 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 23:51 [PATCH 5.4 0/6] Fix build due to clang -Qunused-arguments change Nathan Chancellor
2025-08-11 23:51 ` [PATCH 5.4 1/6] ARM: 9448/1: Use an absolute path to unified.h in KBUILD_AFLAGS Nathan Chancellor
2025-08-12 4:12 ` Sasha Levin
2025-08-11 23:51 ` [PATCH 5.4 2/6] kbuild: Update assembler calls to use proper flags and language target Nathan Chancellor
2025-08-12 4:12 ` Sasha Levin
2025-08-12 21:18 ` Nathan Chancellor
2025-08-11 23:51 ` [PATCH 5.4 3/6] mips: Include KBUILD_CPPFLAGS in CHECKFLAGS invocation Nathan Chancellor
2025-08-12 4:12 ` Sasha Levin
2025-08-11 23:51 ` [PATCH 5.4 4/6] kbuild: Add CLANG_FLAGS to as-instr Nathan Chancellor
2025-08-12 4:12 ` Sasha Levin
2025-08-11 23:51 ` [PATCH 5.4 5/6] kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS Nathan Chancellor
2025-08-12 4:12 ` Sasha Levin
2025-08-12 21:11 ` Nathan Chancellor [this message]
2025-08-11 23:51 ` [PATCH 5.4 6/6] kbuild: Add KBUILD_CPPFLAGS to as-option invocation Nathan Chancellor
2025-08-12 4:12 ` Sasha Levin
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=20250812211145.GB532342@ax162 \
--to=nathan@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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