stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mark Brown <broonie@kernel.org>
Cc: kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, stable@vger.kernel.org
Subject: Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
Date: Thu, 21 Sep 2017 17:10:06 +0200	[thread overview]
Message-ID: <20170921151006.GB7791@kroah.com> (raw)
In-Reply-To: <20170921142129.zpv75rjgzkypmcjf@sirena.co.uk>

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.

thanks,

greg k-h

  reply	other threads:[~2017-09-21 15:09 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 [this message]
2017-10-04 13:36       ` Arnd Bergmann
2017-10-04 14:38         ` Greg KH

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=20170921151006.GB7791@kroah.com \
    --to=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).