From: Greg KH <greg@kroah.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Mark Brown <broonie@kernel.org>,
linaro-kernel@lists.linaro.org,
"# 3.4.x" <stable@vger.kernel.org>,
Kernel Build Reports Mailman List
<kernel-build-reports@lists.linaro.org>
Subject: Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
Date: Wed, 4 Oct 2017 16:38:03 +0200 [thread overview]
Message-ID: <20171004143803.GA13707@kroah.com> (raw)
In-Reply-To: <CAK8P3a30AVNhgDb0s_HoSgPjUn+ajfHe_YjKcWiR2p8JYz8TAw@mail.gmail.com>
On Wed, Oct 04, 2017 at 03:36:13PM +0200, Arnd Bergmann wrote:
> On Thu, Sep 21, 2017 at 5:10 PM, Greg KH <greg@kroah.com> wrote:
> > On Thu, Sep 21, 2017 at 03:21:29PM +0100, Mark Brown wrote:
> >> On Thu, Sep 21, 2017 at 09:26:41AM +0200, Greg KH wrote:
> >> > On Wed, Sep 20, 2017 at 06:42:48PM +0100, Build bot for Mark Brown wrote:
> >>
> >> > > Warnings Summary: 1
> >> > > 1 ../drivers/staging/media/imx/imx-media-of.c:216:4: warning: 'remote_np' may be used uninitialized in this function [-Wmaybe-uninitialized]
> >>
> >> > I'm guessing that same warning is also in Linus's tree?
> >>
> >> Not currently, Linus' tree (and -next) are totally clean in my builds.
> >> It does look like it was in baseline v4.13 though.
> >
> > Hm, it looks like 0b2e9e7947e7 ("media: staging/imx: remove confusing
> > IS_ERR_OR_NULL usage") moved things around a bit so that gcc now can
> > tell that this variable is used.
> >
> > I'll just ignore it for now, that commit isn't really a good one for
> > stable trees.
>
> I just sent a trivial workaround for v4.13. Sorry for not having addressed
> this earlier, my test box had the patch that went upstream in 4.14, so I
> failed to see this in my own build reports.
Thanks for that, I'll queue it up in the next round of kernels after
these are released.
greg k-h
prev parent reply other threads:[~2017-10-04 14:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 17:42 v4.13.3 build: 0 failures 1 warnings (v4.13.3) Build bot for Mark Brown
2017-09-21 7:26 ` Greg KH
2017-09-21 14:21 ` Mark Brown
2017-09-21 15:10 ` Greg KH
2017-10-04 13:36 ` Arnd Bergmann
2017-10-04 14:38 ` Greg KH [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=20171004143803.GA13707@kroah.com \
--to=greg@kroah.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.