linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 09/14] staging:iio:buffers switch select kconfig elements to depends.
Date: Wed, 25 Apr 2012 11:02:35 +0200	[thread overview]
Message-ID: <4F97BDAB.9050506@metafoo.de> (raw)
In-Reply-To: <1335096819-19565-10-git-send-email-jic23@kernel.org>

On 04/22/2012 02:13 PM, Jonathan Cameron wrote:
> As we are moving the IIO core out of staging, we need to
> stop drivers in staging controlling whether elements of the
> core are built.
> 
> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
> ---
>  drivers/staging/iio/Kconfig |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/iio/Kconfig b/drivers/staging/iio/Kconfig
> index fe15867..e644508 100644
> --- a/drivers/staging/iio/Kconfig
> +++ b/drivers/staging/iio/Kconfig
> @@ -28,7 +28,7 @@ config IIO_BUFFER
>  if IIO_BUFFER
>  
>  config IIO_SW_RING
> -       select IIO_TRIGGER
> +        depends on IIO_TRIGGER
>  	tristate "Industrial I/O lock free software ring"
>  	help
>  	  Example software ring buffer implementation.  The design aim
> @@ -37,7 +37,7 @@ config IIO_SW_RING
>  	  in interrupt context.
>  
>  config IIO_KFIFO_BUF
> -	select IIO_TRIGGER
> +	depends on IIO_TRIGGER
>  	tristate "Industrial I/O buffering based on kfifo"
>  	help
>  	  A simple fifo based on kfifo.  Use this if you want a fifo


Is there actually anything in the code which gets enabled by these config
symbols that depends on IIO_TRIGGER?

- Lars

  reply	other threads:[~2012-04-25  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 12:13 [PATCH 00/14] IIO: Move from staging to drivers/iio Jonathan Cameron
2012-04-22 12:13 ` [PATCH 01/14] staging:iio:accel switch select kconfig elements to depends Jonathan Cameron
2012-04-22 12:13 ` [PATCH 06/14] staging:iio:impedance-analyzer " Jonathan Cameron
2012-04-22 12:13 ` [PATCH 07/14] staging:iio:imu " Jonathan Cameron
2012-04-22 12:13 ` [PATCH 08/14] staging:iio:meter " Jonathan Cameron
2012-04-22 12:13 ` [PATCH 09/14] staging:iio:buffers " Jonathan Cameron
2012-04-25  9:02   ` Lars-Peter Clausen [this message]
2012-04-25 15:00     ` Jonathan Cameron
2012-04-22 12:13 ` [PATCH 11/14] staging:iio:Documentation Trivial typo fixes Jonathan Cameron
2012-04-25  9:00 ` [PATCH 00/14] IIO: Move from staging to drivers/iio Lars-Peter Clausen
2012-04-25 10:04   ` Jonathan Cameron
2012-04-25 11:47     ` Lars-Peter Clausen
2012-04-25 15:03       ` 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=4F97BDAB.9050506@metafoo.de \
    --to=lars@metafoo.de \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.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).