From: Greg KH <gregkh@linuxfoundation.org>
To: Build bot for 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 15:05:34 +0200 [thread overview]
Message-ID: <20180411130534.GA8683@kroah.com> (raw)
In-Reply-To: <E1f66Zr-0000XT-6t@optimist>
On Wed, Apr 11, 2018 at 04:37:43AM +0100, Build bot for Mark Brown wrote:
> Tree/Branch: v4.15.16
> Git describe: v4.15.16
> Commit: 49859d3c55 Linux 4.15.16
>
> Build Time: 85 min 9 sec
>
> Passed: 5 / 11 ( 45.45 %)
> Failed: 6 / 11 ( 54.55 %)
>
> Errors: 57
> Warnings: 2
> Section Mismatches: 0
>
> Failed defconfigs:
> arm64-allmodconfig
> arm-multi_v5_defconfig
> arm-multi_v7_defconfig
> arm-allmodconfig
> x86_64-allmodconfig
> arm64-defconfig
>
> Errors:
>
> 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?
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?
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-11 13:28 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 [this message]
2018-04-11 16:00 ` Mark Brown
2018-04-11 17:51 ` 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=20180411130534.GA8683@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.