From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>
Subject: Re: Build failures in stable queues (4.4.y and later)
Date: Fri, 31 Aug 2018 13:22:10 -0700 [thread overview]
Message-ID: <20180831202210.GA30176@kroah.com> (raw)
In-Reply-To: <20180831201905.GA25259@roeck-us.net>
On Fri, Aug 31, 2018 at 01:19:05PM -0700, Guenter Roeck wrote:
> On Fri, Aug 31, 2018 at 01:07:28PM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Aug 31, 2018 at 08:47:59AM -0700, Guenter Roeck wrote:
> > > One more build failure in v4.9.y.queue:
> > >
> > >
> > > Build reference: v4.9.124-64-g6d66e98
> > > gcc version: sparc64-linux-gcc (GCC) 7.3.0
> > >
> > > Building sparc32:allmodconfig ... passed
> > > Building sparc32:defconfig ... failed
> > > --------------
> > > Error log:
> > >
> > > arch/sparc/kernel/pcic.c: In function 'pcibios_fixup_bus':
> > > arch/sparc/kernel/pcic.c:647:8: error: 'cmd' may be used uninitialized in this function
> >
> > That is really odd as there is no patch in the queue that touches this
> > file. Could this have been caused by an older release?
> >
>
> Ah, yes, sorry. I had added sparc32:defconfig recently since
> sparc32:allmodconfig no longer builds in mainline. The fix is
> commit 2dc77533f1e4 ("sparc: kernel/pcic: silence gcc 7.x
> warning in pcibios_fixup_bus()"). The patch applies cleanly
> to v4.9.y and fixes the problem.
No problem, I'll go queue that up now.
greg k-h
next prev parent reply other threads:[~2018-09-01 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 13:47 Build failures in stable queues (4.4.y and later) Guenter Roeck
2018-08-31 14:57 ` Guenter Roeck
2018-08-31 15:47 ` Guenter Roeck
2018-08-31 20:07 ` Greg Kroah-Hartman
2018-08-31 20:19 ` Guenter Roeck
2018-08-31 20:22 ` Greg Kroah-Hartman [this message]
2018-08-31 15:58 ` Greg Kroah-Hartman
2018-08-31 19:56 ` Greg Kroah-Hartman
2018-08-31 20: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=20180831202210.GA30176@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux@roeck-us.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