From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: perf-users <perf-users@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
linux-stable <stable@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Sasha Levin <sashal@kernel.org>, Leo Yan <leo.yan@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: perf: bench/sched-messaging.c:73:13: error: 'dummy' may be used uninitialized
Date: Tue, 13 Jul 2021 17:17:57 +0200 [thread overview]
Message-ID: <YO2upa4SZWS59KeB@kroah.com> (raw)
In-Reply-To: <CA+G9fYubOg+Pu8N3LYFKn-eL3f=gn4ceK9Asj1RdBDntU_A2ng@mail.gmail.com>
On Tue, Jul 13, 2021 at 08:40:28PM +0530, Naresh Kamboju wrote:
> LKFT have noticed these warnings / errors when we have updated gcc version from
> gcc-9 to gcc-11 on stable-rc linux-5.4.y branch. I have provided the steps to
> reproduce in this email below.
>
> Following perf builds failed with gcc-11 with linux-5.4.y branch.
> - build-arm-gcc-11-perf
> - build-arm64-gcc-11-perf
> - build-i386-gcc-11-perf
> - build-x86-gcc-11-perf
>
> Build error log:
> --------------------
<snip>
I imagine this is fixed in newer kernel versions, so if you could
provide the git ids of the patches needed to fix this up in 5.4, that
would be great!
thanks,
greg k-h
next prev parent reply other threads:[~2021-07-13 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 15:10 perf: bench/sched-messaging.c:73:13: error: 'dummy' may be used uninitialized Naresh Kamboju
2021-07-13 15:17 ` Greg Kroah-Hartman [this message]
2021-07-13 15:32 ` Anders Roxell
2021-07-15 11:05 ` Greg Kroah-Hartman
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=YO2upa4SZWS59KeB@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=perf-users@linaro.org \
--cc=peterz@infradead.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