From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: Michael Zoran <mzoran@crowfest.net>,
kernel-build-reports@lists.linaro.org,
linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org
Subject: Re: next-20170201 build: 3 failures 3 warnings (next-20170201)
Date: Wed, 1 Feb 2017 12:17:52 +0100 [thread overview]
Message-ID: <20170201111752.GI13721@kroah.com> (raw)
In-Reply-To: <20170201105627.pmx2c2wjfxjvnujq@sirena.org.uk>
On Wed, Feb 01, 2017 at 10:56:27AM +0000, Mark Brown wrote:
> On Wed, Feb 01, 2017 at 10:38:07AM +0000, Build bot for Mark Brown wrote:
>
> Today's -next fails to build both arm and arm64 allmodconfigs due to:
>
> > arm64-allmodconfig
> > ../drivers/staging/bcm2835-audio/bcm2835-vchiq.c:97:9: error: implicit declaration of function 'vchi_msg_queue' [-Werror=implicit-function-declaration]
>
> > arm-allmodconfig
> > ../drivers/staging/bcm2835-audio/bcm2835-vchiq.c:97:9: error: implicit declaration of function 'vchi_msg_queue' [-Werror=implicit-function-declaration]
> > ../drivers/staging/media/platform/bcm2835/mmal-vchiq.c:453:8: error: implicit declaration of function 'vchi_msg_queue' [-Werror=implicit-function-declaration]
>
> caused by that driver being added.
Doesn't look like vchi_msg_queue is ever exported for modules to use.
Michael, care to make up a patch for that?
Also, the build warning is odd, shouldn't the include files point to the
correct .h file for this?
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-01 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 10:38 next-20170201 build: 3 failures 3 warnings (next-20170201) Build bot for Mark Brown
2017-02-01 10:56 ` Mark Brown
2017-02-01 11:17 ` Greg Kroah-Hartman [this message]
2017-02-01 13:45 ` Michael Zoran
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=20170201111752.GI13721@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=mzoran@crowfest.net \
/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