From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, llvm@lists.linux.dev,
Masahiro Yamada <masahiroy@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: Apply clang '--target=' KBUILD_CPPFLAGS shuffle to linux-6.4.y and linux-6.3.y
Date: Sun, 16 Jul 2023 17:02:23 +0200 [thread overview]
Message-ID: <2023071606-relative-facsimile-f994@gregkh> (raw)
In-Reply-To: <20230703150339.GA1975402@dev-arch.thelio-3990X>
On Mon, Jul 03, 2023 at 08:03:39AM -0700, Nathan Chancellor wrote:
> Hi Greg and Sasha,
>
> Please consider applying the following patches to 6.4 and 6.3, they
> should apply cleanly.
>
> 08f6554ff90e ("mips: Include KBUILD_CPPFLAGS in CHECKFLAGS invocation")
> a7e5eb53bf9b ("powerpc/vdso: Include CLANG_FLAGS explicitly in ldflags-y")
> cff6e7f50bd3 ("kbuild: Add CLANG_FLAGS to as-instr")
> 43fc0a99906e ("kbuild: Add KBUILD_CPPFLAGS to as-option invocation")
> feb843a469fb ("kbuild: add $(CLANG_FLAGS) to KBUILD_CPPFLAGS")
>
> They resolve and help avoid build breakage with tip of tree clang, which
> has become a little stricter in the flags that it will accept for a
> particular target, which requires '--target=' to be passed along to all
> invocations of $(CC). Our continuous integration does not currently show
> any breakage with 6.1 and earlier; should these patches be needed there,
> I will send them at a later time.
6.3.y is now end-of-life, but I've queued these up for 6.4.y, thanks.
greg k-h
prev parent reply other threads:[~2023-07-16 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:03 Apply clang '--target=' KBUILD_CPPFLAGS shuffle to linux-6.4.y and linux-6.3.y Nathan Chancellor
2023-07-16 15:02 ` Greg Kroah-Hartman [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=2023071606-relative-facsimile-f994@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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