From: Hanjun Guo <hanjun.guo@linaro.org>
To: Mark Brown <broonie@kernel.org>, Y Vo <yvo@apm.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: 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 15:33:52 +0800 [thread overview]
Message-ID: <5577E860.1040605@linaro.org> (raw)
In-Reply-To: <20150609182305.GW14071@sirena.org.uk>
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:
From d47771429144d80a2c38b79f06577dd237e349d1 Mon Sep 17 00:00:00 2001
From: Hanjun Guo <hanjun.guo@linaro.org>
Date: Wed, 10 Jun 2015 15:24:30 +0800
Subject: [PATCH] GPIO / ACPI: export acpi_gpiochip_request(free)_interrupts
for module use
acpi_gpiochip_request(free)_interrupts can be used for modules,
so export them. This also fixs a compile error when xgene-sb
configured as kernel module.
Fixes: 733cf014f020 "gpio: xgene: add ACPI support for APM X-Gene GPIO
standby driver"
Signed-off-by: Hanjun Guo <hanjun.guo@linaro.org>
---
drivers/gpio/gpiolib-acpi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
index 19b99d0..980a996 100644
--- a/drivers/gpio/gpiolib-acpi.c
+++ b/drivers/gpio/gpiolib-acpi.c
@@ -307,6 +307,7 @@ void acpi_gpiochip_request_interrupts(struct
gpio_chip *chip)
acpi_walk_resources(handle, "_AEI",
acpi_gpiochip_request_interrupt, acpi_gpio);
}
+EXPORT_SYMBOL_GPL(acpi_gpiochip_request_interrupts);
/**
* acpi_gpiochip_free_interrupts() - Free GPIO ACPI event interrupts.
@@ -346,6 +347,7 @@ void acpi_gpiochip_free_interrupts(struct gpio_chip
*chip)
kfree(event);
}
}
+EXPORT_SYMBOL_GPL(acpi_gpiochip_free_interrupts);
int acpi_dev_add_driver_gpios(struct acpi_device *adev,
const struct acpi_gpio_mapping *gpios)
--
1.9.1
next prev parent reply other threads:[~2015-06-10 7:34 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 ` Hanjun Guo [this message]
2015-06-10 8:43 ` [Linaro-acpi] " 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=5577E860.1040605@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).