From: Mark Brown <broonie@kernel•org>
To: Y Vo <yvo@apm•com>, Linus Walleij <linus.walleij@linaro•org>
Cc: kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linaro-acpi@lists•linaro.org
Subject: Re: next-20150609 build: 2 failures 40 warnings (next-20150609)
Date: Tue, 9 Jun 2015 19:23:05 +0100 [thread overview]
Message-ID: <20150609182305.GW14071@sirena.org.uk> (raw)
In-Reply-To: <E1Z2Ny7-00019f-Dj@optimist>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Tue, Jun 09, 2015 at 07:09:47PM +0100, Build bot for Mark Brown wrote:
> arm64-allmodconfig
> ERROR: "acpi_gpiochip_request_interrupts" [drivers/gpio/gpio-xgene-sb.ko] undefined!
> ERROR: "acpi_gpiochip_free_interrupts" [drivers/gpio/gpio-xgene-sb.ko] undefined!
Today's -next fails to build an arm64 allmodconfig due to commit
733cf014f02040b3ad (gpio: xgene: add ACPI support for APM X-Gene GPIO
standby driver) which adds ACPI support to the X-Gene standby driver
without either adding a dependency on ACPI or there being stubs in the
ACPI headers for the above functions in !ACPI configurations. My
instinct is that the stubs are going to be nicer since it'll save on
ifdefs in drivers which seems nicer.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-06-09 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 18:09 next-20150609 build: 2 failures 40 warnings (next-20150609) Build bot for Mark Brown
2015-06-09 18:23 ` Mark Brown [this message]
2015-06-10 7:33 ` [Linaro-acpi] " Hanjun Guo
2015-06-10 8:43 ` Y Vo
2015-06-10 9:02 ` Hanjun Guo
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=20150609182305.GW14071@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linaro-acpi@lists$(echo .)linaro.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=yvo@apm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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