From: Nathan Chancellor <nathan@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Marc Zyngier <maz@kernel.org>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, kbuild-all@lists.01.org,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [arm-platforms:hack/m1-pmu 8/8] drivers/perf/apple_m1_cpu_pmu.c:100:32: warning: initializer overrides prior initialization of this subobject
Date: Sun, 14 Nov 2021 14:42:06 -0700 [thread overview]
Message-ID: <YZGCrpVfY5xng4EC@archlinux-ax161> (raw)
In-Reply-To: <CANiq72nhQuRPgVMqDkr9OZqSLpT_2VVwkBaY97PbuqhbuNJnJg@mail.gmail.com>
On Sun, Nov 14, 2021 at 01:24:16PM +0100, Miguel Ojeda wrote:
> On Sun, Nov 14, 2021 at 12:07 PM Ard Biesheuvel <ardb@kernel.org> wrote:
> >
> > +KBUILD_CFLAGS += $(call cc-option, -Wno-initializer-overrides)
>
> I don't think we would need `cc-option`.
-Winitializer-overrides is the clang version of the flag, as opposed to
-Woverride-init for gcc. A compatibility flag was added in clang 8 so if
this is changed to
KBUILD_CFLAGS += -Wno-override-init
it should work for both compilers.
Cheers,
Nathan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-11-14 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 8:25 [arm-platforms:hack/m1-pmu 8/8] drivers/perf/apple_m1_cpu_pmu.c:100:32: warning: initializer overrides prior initialization of this subobject kernel test robot
2021-11-14 10:10 ` Marc Zyngier
2021-11-14 11:07 ` Ard Biesheuvel
2021-11-14 12:24 ` Miguel Ojeda
2021-11-14 21:42 ` Nathan Chancellor [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=YZGCrpVfY5xng4EC@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
/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