From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:40217 "EHLO
        out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1752289AbdJDOhy (ORCPT
        <rfc822;stable@vger.kernel.org>); Wed, 4 Oct 2017 10:37:54 -0400
Date: Wed, 4 Oct 2017 16:38:03 +0200
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)
Message-ID: <20171004143803.GA13707@kroah.com>
References: <E1duj1M-00007p-1f@optimist>
 <20170921072641.GD4588@kroah.com>
 <20170921142129.zpv75rjgzkypmcjf@sirena.co.uk>
 <20170921151006.GB7791@kroah.com>
 <CAK8P3a30AVNhgDb0s_HoSgPjUn+ajfHe_YjKcWiR2p8JYz8TAw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAK8P3a30AVNhgDb0s_HoSgPjUn+ajfHe_YjKcWiR2p8JYz8TAw@mail.gmail.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

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