All of lore.kernel.org
 help / color / mirror / Atom feed
* v4.13.3 build: 0 failures 1 warnings (v4.13.3)
@ 2017-09-20 17:42 Build bot for Mark Brown
  2017-09-21  7:26 ` Greg KH
  0 siblings, 1 reply; 6+ messages in thread
From: Build bot for Mark Brown @ 2017-09-20 17:42 UTC (permalink / raw)
  To: kernel-build-reports, linaro-kernel, stable

Tree/Branch: v4.13.3
Git describe: v4.13.3
Commit: 56b9b16136 Linux 4.13.3

Build Time: 101 min 18 sec

Passed:   10 / 10   (100.00 %)
Failed:    0 / 10   (  0.00 %)

Errors: 0
Warnings: 1
Section Mismatches: 0

-------------------------------------------------------------------------------
defconfigs with issues (other than build errors):
      1 warnings    0 mismatches  : arm-allmodconfig

-------------------------------------------------------------------------------

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]



===============================================================================
Detailed per-defconfig build reports below:


-------------------------------------------------------------------------------
arm-allmodconfig : PASS, 0 errors, 1 warnings, 0 section mismatches

Warnings:
	../drivers/staging/media/imx/imx-media-of.c:216:4: warning: 'remote_np' may be used uninitialized in this function [-Wmaybe-uninitialized]
-------------------------------------------------------------------------------

Passed with no errors, warnings or mismatches:

arm64-allnoconfig
arm64-allmodconfig
arm-multi_v5_defconfig
arm-multi_v7_defconfig
x86_64-defconfig
arm-allnoconfig
x86_64-allnoconfig
arm-multi_v4t_defconfig
arm64-defconfig
close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
  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
  0 siblings, 1 reply; 6+ messages in thread
From: Greg KH @ 2017-09-21  7:26 UTC (permalink / raw)
  To: Build bot for Mark Brown; +Cc: kernel-build-reports, linaro-kernel, stable

On Wed, Sep 20, 2017 at 06:42:48PM +0100, Build bot for Mark Brown wrote:
> Tree/Branch: v4.13.3
> Git describe: v4.13.3
> Commit: 56b9b16136 Linux 4.13.3
> 
> Build Time: 101 min 18 sec
> 
> Passed:   10 / 10   (100.00 %)
> Failed:    0 / 10   (  0.00 %)
> 
> Errors: 0
> Warnings: 1
> Section Mismatches: 0
> 
> -------------------------------------------------------------------------------
> defconfigs with issues (other than build errors):
>       1 warnings    0 mismatches  : arm-allmodconfig
> 
> -------------------------------------------------------------------------------
> 
> 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?

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
  2017-09-21  7:26 ` Greg KH
@ 2017-09-21 14:21   ` Mark Brown
  2017-09-21 15:10     ` Greg KH
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2017-09-21 14:21 UTC (permalink / raw)
  To: Greg KH; +Cc: kernel-build-reports, linaro-kernel, stable

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
  2017-09-21 14:21   ` Mark Brown
@ 2017-09-21 15:10     ` Greg KH
  2017-10-04 13:36       ` Arnd Bergmann
  0 siblings, 1 reply; 6+ messages in thread
From: Greg KH @ 2017-09-21 15:10 UTC (permalink / raw)
  To: Mark Brown; +Cc: kernel-build-reports, linaro-kernel, stable

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
  2017-09-21 15:10     ` Greg KH
@ 2017-10-04 13:36       ` Arnd Bergmann
  2017-10-04 14:38         ` Greg KH
  0 siblings, 1 reply; 6+ messages in thread
From: Arnd Bergmann @ 2017-10-04 13:36 UTC (permalink / raw)
  To: Greg KH
  Cc: Mark Brown, linaro-kernel, # 3.4.x, Kernel Build Reports Mailman List

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.

      Arnd

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: v4.13.3 build: 0 failures 1 warnings (v4.13.3)
  2017-10-04 13:36       ` Arnd Bergmann
@ 2017-10-04 14:38         ` Greg KH
  0 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2017-10-04 14:38 UTC (permalink / raw)
  To: Arnd Bergmann
  Cc: Mark Brown, linaro-kernel, # 3.4.x, Kernel Build Reports Mailman List

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2017-10-04 14:37 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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.