From: gregkh <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Olof's autobuilder" <build@lixom.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"# 3.4.x" <stable@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>
Subject: Re: stable-rc build: 132 warnings 0 failures (stable-rc/v4.9.52-65-gaceea42)
Date: Thu, 5 Oct 2017 11:14:56 +0200 [thread overview]
Message-ID: <20171005091456.GB26886@kroah.com> (raw)
In-Reply-To: <CAK8P3a0Kkf-oF8L9VdCXx23phW2nuF3ocT_nUUuTUUqqsyjogQ@mail.gmail.com>
On Wed, Oct 04, 2017 at 04:39:06PM +0200, Arnd Bergmann wrote:
> On Wed, Oct 4, 2017 at 9:50 AM, Olof's autobuilder <build@lixom.net> wrote:
>
> It seems a couple of warnings are now present due to the use of gcc-7,
> here are the respective patches we want backported:
>
> > Warnings:
> >
> > 1 include/asm-generic/bitops/non-atomic.h:105:34: warning: 'shadow' may be used uninitialized in this function [-Wmaybe-uninitialized]
>
> f6aafac184a3 ("IB/qib: fix false-postive maybe-uninitialized warning")
>
> > 4 arch/arm/mach-bcm/bcm_kona_smc.c:36:34: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
> > 5 arch/arm/mach-omap2/prm_common.c:716:34: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
> > 5 arch/arm/mach-omap2/vc.c:562:35: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
> > 7 arch/arm/mach-spear/time.c:207:34: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
> > 8 arch/arm/mach-at91/pm.c:338:34: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
> > 2 arch/arm/mach-cns3xxx/core.c:349:36: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
>
> 0527873b29b0 ("ARM: remove duplicate 'const' annotations'")
>
> > 2 sound/soc/codecs/rt5514.c:398:14: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
>
> 03ba791df98d ("ASoC: rt5514: fix gcc-7 warning")
>
> > 2 sound/soc/codecs/rt5659.c:1153:14: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
>
> eae39b5f4269 ("ASoC: rt5659: drop double const")
>
> > 2 sound/soc/codecs/rt5660.c:529:14: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
> > 2 sound/soc/codecs/rt5660.c:532:14: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier]
>
> 4281fcc02ed9 ("ASoC: rt5660: remove double const")
>
> > 3 sound/pci/au88x0/au88x0_core.c:2304:68: warning: 'mix[0]' may be used uninitialized in this function [-Wmaybe-uninitialized]
> > 3 sound/pci/au88x0/au88x0_core.c:2305:58: warning: 'src[0]' may be used uninitialized in this function [-Wmaybe-uninitialized]
>
> 13f99ebdd602 ("ALSA: au88x0: avoid theoretical uninitialized access")
Thanks for these, all now queued up.
greg k-h
prev parent reply other threads:[~2017-10-05 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <59d492aa.8340620a.cde03.0bf2@mx.google.com>
2017-10-04 14:39 ` Arnd Bergmann
2017-10-05 9:14 ` gregkh [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=20171005091456.GB26886@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=build@lixom.net \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--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
all inboxes | Powered by JetHome®