Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 4/5] iio: remove mention of ring buffer from  CONFIG_IIO_KFIFO_BUF, CONFIG_IIO_TRIGGER description
Date: Sat, 29 Jun 2013 13:15:59 +0100	[thread overview]
Message-ID: <51CECFFF.2060803@kernel.org> (raw)
In-Reply-To: <1372022900-18670-4-git-send-email-pmeerw@pmeerw.net>

On 06/23/2013 10:28 PM, Peter Meerwald wrote:
> ring buffers are only in staging, don't mention them here
Actually they aren't there either any more.  Long killed off.

> 
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
Applied to the togreg branch of iio.git

Thanks
> ---
>  drivers/iio/Kconfig | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
> index be8e303..524380c 100644
> --- a/drivers/iio/Kconfig
> +++ b/drivers/iio/Kconfig
> @@ -30,8 +30,7 @@ config IIO_KFIFO_BUF
>  	select IIO_TRIGGER
>  	tristate "Industrial I/O buffering based on kfifo"
>  	help
> -	  A simple fifo based on kfifo.  Use this if you want a fifo
> -	  rather than a ring buffer. Note that this currently provides
> +	  A simple fifo based on kfifo.  Note that this currently provides
>  	  no buffer events so it is up to userspace to work out how
>  	  often to read from the buffer.
>  
> @@ -49,7 +48,7 @@ config IIO_TRIGGER
>  	help
>  	  Provides IIO core support for triggers.  Currently these
>  	  are used to initialize capture of samples to push into
> -	  ring buffers.  The triggers are effectively a 'capture
> +	  buffers.  The triggers are effectively a 'capture
>  	  data now' interrupt.
>  
>  config IIO_CONSUMERS_PER_TRIGGER
> 

  reply	other threads:[~2013-06-29 12:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-23 21:28 [PATCH 1/5] iio: fix typos in dac Kconfig Peter Meerwald
2013-06-23 21:28 ` [PATCH 2/5] iio: use I2C_FUNC_SMBUS_I2C_BLOCK macro Peter Meerwald
2013-06-29  9:51   ` Jonathan Cameron
2013-06-29 23:05     ` Ge Gao
2013-06-23 21:28 ` [PATCH 3/5] iio: fix Kconfig typos Peter Meerwald
2013-06-29 10:08   ` Jonathan Cameron
2013-06-23 21:28 ` [PATCH 4/5] iio: remove mention of ring buffer from CONFIG_IIO_KFIFO_BUF, CONFIG_IIO_TRIGGER description Peter Meerwald
2013-06-29 12:15   ` Jonathan Cameron [this message]
2013-06-23 21:28 ` [PATCH 5/5] iio: reword help text of several IIO_ST drivers Peter Meerwald
2013-06-24  6:30   ` Denis CIOCCA
2013-06-29 12:17     ` Jonathan Cameron
2013-06-24  6:18 ` [PATCH 1/5] iio: fix typos in dac Kconfig Lars-Peter Clausen
2013-06-29  9:49   ` 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=51CECFFF.2060803@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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