From: Jonathan Cameron <jic23@kernel.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] Fix build failure for gp2ap020a00f.c
Date: Mon, 02 Dec 2013 21:13:14 +0000 [thread overview]
Message-ID: <529CF7EA.6090500@kernel.org> (raw)
In-Reply-To: <20131202112558.GF16735@n2100.arm.linux.org.uk>
On 12/02/13 11:25, Russell King - ARM Linux wrote:
> drivers/built-in.o: In function `gp2ap020a00f_thresh_event_handler':
> powercap_sys.c:(.text+0x15f90c): undefined reference to `irq_work_queue'
> make[1]: *** [vmlinux] Error 1
> make[1]: Target `uImage' not remade because of errors.
> make: *** [sub-make] Error 2
> make: Target `uImage' not remade because of errors.
>
> You need the IRQ work support, but GP2AP020A00F is not selecting this
> symbol.
>
> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Thanks Russell,
Applied to the fixes-togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
Jonathan
> ---
> drivers/iio/light/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/iio/light/Kconfig b/drivers/iio/light/Kconfig
> index b0d65df3ede2..a022f27c6690 100644
> --- a/drivers/iio/light/Kconfig
> +++ b/drivers/iio/light/Kconfig
> @@ -43,6 +43,7 @@ config GP2AP020A00F
> depends on I2C
> select IIO_BUFFER
> select IIO_TRIGGERED_BUFFER
> + select IRQ_WORK
> help
> Say Y here if you have a Sharp GP2AP020A00F proximity/ALS combo-chip
> hooked to an I2C bus.
>
prev parent reply other threads:[~2013-12-02 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 11:25 [PATCH] Fix build failure for gp2ap020a00f.c Russell King - ARM Linux
2013-12-02 21:13 ` Jonathan Cameron [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=529CF7EA.6090500@kernel.org \
--to=jic23@kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.