From: Jonathan Cameron <jic23@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-iio@vger.kernel.org, Jack Andersen <jackoalan@gmail.com>,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH] iio: adc: dln2-adc: fix build error
Date: Sun, 8 Oct 2017 11:44:03 +0100 [thread overview]
Message-ID: <20171008114403.68002f32@archlinux> (raw)
In-Reply-To: <af332f59-daae-1140-cb89-ebc179b0d2f4@infradead.org>
On Sat, 7 Oct 2017 16:53:20 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> The dln2-adc driver uses interface(s) that are controlled by the
> IIO_TRIGGERED_BUFFER Kconfig symbol, so the driver needs to select
> that symbol to prevent the build error.
>
> drivers/iio/adc/dln2-adc.o: In function `dln2_adc_probe':
> dln2-adc.c:(.text+0x528): undefined reference to `devm_iio_triggered_buffer_setup'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Cc: Jonathan Cameron <jic23@kernel.org>
> Cc: linux-iio@vger.kernel.org
> Cc: Jack Andersen <jackoalan@gmail.com>
Applied to the fixes-togreg branch of iio.git.
Thanks,
Jonathan
> ---
> drivers/iio/adc/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- lnx-414-rc3.orig/drivers/iio/adc/Kconfig
> +++ lnx-414-rc3/drivers/iio/adc/Kconfig
> @@ -243,6 +243,8 @@ config DA9150_GPADC
> config DLN2_ADC
> tristate "Diolan DLN-2 ADC driver support"
> depends on MFD_DLN2
> + select IIO_BUFFER
> + select IIO_TRIGGERED_BUFFER
> help
> Say yes here to build support for Diolan DLN-2 ADC.
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-10-08 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 23:53 [PATCH] iio: adc: dln2-adc: fix build error Randy Dunlap
2017-10-08 10:44 ` 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=20171008114403.68002f32@archlinux \
--to=jic23@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=jackoalan@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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).