All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
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.15.16 build: 6 failures 2 warnings (v4.15.16)
Date: Wed, 11 Apr 2018 19:51:42 +0200	[thread overview]
Message-ID: <20180411175142.GB21729@kroah.com> (raw)
In-Reply-To: <20180411160014.GB12166@sirena.org.uk>

On Wed, Apr 11, 2018 at 05:00:14PM +0100, Mark Brown wrote:
> On Wed, Apr 11, 2018 at 03:05:34PM +0200, Greg KH wrote:
> > On Wed, Apr 11, 2018 at 04:37:43AM +0100, Build bot for Mark Brown wrote:
> 
> > > 	arm64-allmodconfig
> > > ../include/media/cec.h:94:24: error: 'CEC_EVENT_PIN_HPD_HIGH' undeclared here (not in a function)
> > > ../include/media/cec.h:94:24: error: 'CEC_EVENT_PIN_HPD_HIGH' undeclared here (not in a function)
> > > ../include/media/cec.h:94:24: error: 'CEC_EVENT_PIN_HPD_HIGH' undeclared here (not in a function)
> > > ../include/media/cec.h:94:24: error: 'CEC_EVENT_PIN_HPD_HIGH' undeclared here (not in a function)
> > > ../include/media/cec.h:94:24: error: 'CEC_EVENT_PIN_HPD_HIGH' undeclared here (not in a function)
> > > ../include/media/cec.h:94:24: error: 'CEC_EVENT_PIN_HPD_HIGH' undeclared here (not in a function)
> 
> > Any hint as to what .c files these are?
> 
> drivers/gpu/drm/bridge/adv7511/adv7511_drv.c appears to have been the
> first one.  Looking at the logs it looks like it might've run out of
> disk space transiently during the build, I've just rerun the test and it
> seems to be OK so it looks like a false positive (and also gone and made
> sure it has a lot more disk space to hopefully prevent that happening
> again).
> 
> > And a bunch of warnings just started showing up for all of these, yet I
> > don't see the warnings in any other build system.  Anything "different"
> > you are suddenly doing here?
> 
> I did add back x86 allmodconfig relatively recently which pushed warning
> counts up but that's the only thing unless I picked up a new x86
> compiler from my distro.  However it's likely to have just been the
> above if it was this specific build that you're noticing.

I saw these errors on all of the latest releases, perhaps it was just a
disk space error.  Let's see if it happens again :)

thanks,

greg k-h

      reply	other threads:[~2018-04-11 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11  3:37 v4.15.16 build: 6 failures 2 warnings (v4.15.16) Build bot for Mark Brown
2018-04-11 13:05 ` Greg KH
2018-04-11 16:00   ` Mark Brown
2018-04-11 17:51     ` 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=20180411175142.GB21729@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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.