From: Hanjun Guo <hanjun.guo@linaro.org>
To: Y Vo <yvo@apm.com>
Cc: Mark Brown <broonie@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linaro-acpi@lists.linaro.org, linaro-kernel@lists.linaro.org,
linux-next@vger.kernel.org,
kernel-build-reports@lists.linaro.org
Subject: Re: [Linaro-acpi] next-20150609 build: 2 failures 40 warnings (next-20150609)
Date: Wed, 10 Jun 2015 17:02:36 +0800 [thread overview]
Message-ID: <5577FD2C.1070208@linaro.org> (raw)
In-Reply-To: <CAL4ahLdOSHXZ+O8Q1gsO9ON=cp+1wHC-Btp4XP-1UjpfM5jEcw@mail.gmail.com>
On 06/10/2015 04:43 PM, Y Vo wrote:
> On Wed, Jun 10, 2015 at 2:33 PM, Hanjun Guo <hanjun.guo@linaro.org> wrote:
>> On 06/10/2015 02:23 AM, Mark Brown wrote:
>>>
>>> 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.
>>
>>
>> It seems that acpi_gpiochip_request_interrupts didn't export
>> so there will be a compile error when xgene-sb compiled as
>> a ko, I prepared a patch below:
>
> Coud you help to submit this patch ?
No problem, will do it right now.
Thanks
Hanjun
prev parent reply other threads:[~2015-06-10 9:02 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
2015-06-10 7:33 ` [Linaro-acpi] " Hanjun Guo
2015-06-10 8:43 ` Y Vo
2015-06-10 9:02 ` Hanjun Guo [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=5577FD2C.1070208@linaro.org \
--to=hanjun.guo@linaro.org \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linaro-acpi@lists.linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-next@vger.kernel.org \
--cc=yvo@apm.com \
/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;
as well as URLs for NNTP newsgroup(s).