From: Nathan Chancellor <nathan@kernel•org>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
llvm@lists•linux.dev
Subject: Re: linux-next: Tree for Jul 14
Date: Thu, 14 Jul 2022 09:05:43 -0700 [thread overview]
Message-ID: <YtA+127QgRifnRBZ@dev-arch.thelio-3990X> (raw)
In-Reply-To: <Ys/42uMzQy+CFTGI@debian>
Hi Sudip,
On Thu, Jul 14, 2022 at 12:07:06PM +0100, Sudip Mukherjee (Codethink) wrote:
> Hi Stephen,
>
> On Thu, Jul 14, 2022 at 06:55:14PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20220713:
>
> Build failures on next-20220714:
<snip>
> x86_64 allmodconfig with clang fails with:
>
> drivers/clk/qcom/gpucc-sm8350.c:111:2: error: initializer element is not a compile-time constant
> gpu_cc_parent,
> ^~~~~~~~~~~~~
> drivers/clk/qcom/gpucc-sm8350.c:126:2: error: initializer element is not a compile-time constant
> gpu_cc_parent,
> ^~~~~~~~~~~~~
I sent https://lore.kernel.org/20220711174004.3047516-1-nathan@kernel.org/
for this a few days ago, it just needs to be picked up.
> arch/x86/kernel/cpu/bugs.c:58:21: error: section attribute is specified on redeclared variable [-Werror,-Wsection]
> DEFINE_PER_CPU(u64, x86_spec_ctrl_current);
> ^
> ./arch/x86/include/asm/nospec-branch.h:283:12: note: previous declaration is here
> extern u64 x86_spec_ctrl_current;
This is now fixed in -tip so it should be fixed in -next tomorrorow:
https://git.kernel.org/tip/db866d3352ec85e821e730e191481cba3a2bfa6e
In the future, consider CC'ing our mailing list (llvm@lists•linux.dev)
for any clang related issues so that we can get them taken care of ASAP,
we have a MAINTAINERS entry for a reason :) thank you for testing with
clang; the more people that use it, hopefully the easier it will be to
get things unbroken.
Cheers,
Nathan
next prev parent reply other threads:[~2022-07-14 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 8:55 linux-next: Tree for Jul 14 Stephen Rothwell
2022-07-14 11:07 ` Sudip Mukherjee (Codethink)
2022-07-14 16:05 ` Nathan Chancellor [this message]
2022-07-14 16:21 ` Sudip Mukherjee
2022-07-14 16:29 ` Nathan Chancellor
2022-07-14 16:55 ` Sudip Mukherjee
2022-07-14 18:26 ` Sudip Mukherjee
2022-07-14 18:51 ` Nick Desaulniers
-- strict thread matches above, loose matches on Subject: below --
2025-07-14 9:30 Stephen Rothwell
2023-07-14 4:15 Stephen Rothwell
2021-07-14 3:25 Stephen Rothwell
2020-07-14 10:03 Stephen Rothwell
2017-07-14 3:58 Stephen Rothwell
2016-07-14 6:18 Stephen Rothwell
2015-07-14 5:41 Stephen Rothwell
2014-07-14 7:17 Stephen Rothwell
2014-07-14 17:50 ` Nick Krause
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=YtA+127QgRifnRBZ@dev-arch.thelio-3990X \
--to=nathan@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=sudipm.mukherjee@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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