From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org, Marek Vasut <marex@denx.de>
Subject: Re: [PATCH v2 2/3] staging:iio:mxs-lradc: Select STMP_DEVICE
Date: Mon, 14 Oct 2013 23:14:40 +0100 [thread overview]
Message-ID: <525C6CD0.1010509@kernel.org> (raw)
In-Reply-To: <1381586159-31120-2-git-send-email-lars@metafoo.de>
On 10/12/13 14:55, Lars-Peter Clausen wrote:
> The MXS ADC driver uses the stmp_reset_block() which is only provided when the
> STMP_DEVICE Kconfig symbol is selected. Hence the driver should select this
> symbol. So far this has not been a problem since the driver depends on ARCH_MXS,
> which already selects STMP_DEVICE, but will become necessary once we allow the
> driver to be built when COMPILE_TEST is selected.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> Cc: Marek Vasut <marex@denx.de>
Applied to the togreg branch of iio.git
Thanks,
> ---
> New in v2
> ---
> drivers/staging/iio/adc/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/iio/adc/Kconfig b/drivers/staging/iio/adc/Kconfig
> index cabc7a3..52d92a1 100644
> --- a/drivers/staging/iio/adc/Kconfig
> +++ b/drivers/staging/iio/adc/Kconfig
> @@ -114,6 +114,7 @@ config LPC32XX_ADC
> config MXS_LRADC
> tristate "Freescale i.MX23/i.MX28 LRADC"
> depends on ARCH_MXS
> + select STMP_DEVICE
> select IIO_BUFFER
> select IIO_TRIGGERED_BUFFER
> help
>
next prev parent reply other threads:[~2013-10-14 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 13:55 [PATCH v2 1/3] staging:iio:spear_adc: Fix sparse warning Lars-Peter Clausen
2013-10-12 13:55 ` [PATCH v2 2/3] staging:iio:mxs-lradc: Select STMP_DEVICE Lars-Peter Clausen
2013-10-14 22:14 ` Jonathan Cameron [this message]
2013-10-12 13:55 ` [PATCH v2 3/3] staging:iio: Allow to build SoC specific drivers when COMPILE_TEST is set Lars-Peter Clausen
2013-10-14 22:15 ` Jonathan Cameron
2013-10-14 22:14 ` [PATCH v2 1/3] staging:iio:spear_adc: Fix sparse warning Jonathan Cameron
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=525C6CD0.1010509@kernel.org \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=marex@denx.de \
/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).