linux-iio.vger.kernel.org archive mirror
 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 3/4] staging:iio: add a callback buffer for in kernel push interface
Date: Fri, 02 Nov 2012 10:53:00 +0000	[thread overview]
Message-ID: <5093A60C.90806@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.01.1210311505340.10186@pmeerw.net>

On 10/31/2012 02:10 PM, Peter Meerwald wrote:
> Hi,
> 
> I'm sure you missed my spellchecking :)
I am always happy to accept fixes like this that mean I don't look as
much of an idiot when patches hit mainline ;)
> 
>> +config IIO_BUFFER_CB
>> +       boolean "IIO callback buffer used for push in kernel interfaces"
>> +       help
>> +         Should be selected by any drivers that do inkernel push
>> +	 usage.  That is, those where the data is pushed to the consumer.
>> +
> 
> is it 'in kernel' or 'inkernel'? I'd prefer in-kernel :)
> indentation seems inconsistent
in-kernel is indeed nicer.  I'll do that here and maybe clean up the other uses later.

> 
>> +/**
>> + * iio_channel_cb_get_channels() - get access to the underlying channels.
>> + * @cb_buff:		The callback buffers from whom we want the channel
>> + *			information.
> 
> buffers from which?

actually should be 'buffer from whom'.
Good catch though - I could have read that 100 times and never noticed.

I'm lazy so won't repost the patch with these changes but will wait a little longer
then merge it if no one shouts loudly that I shouldn't. (they'll be in the wip
branch if anyone actually cares enough to look)

  reply	other threads:[~2012-11-02 10:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 10:30 [PATCH 0/4 V6] staging:iio: Add support for multiple buffers (testing required!) Jonathan Cameron
2012-10-31 10:30 ` [PATCH 1/4] staging:iio: Add support for multiple buffers Jonathan Cameron
2012-10-31 10:30 ` [PATCH 2/4] staging:iio:in kernel users: Add a data field for channel specific info Jonathan Cameron
2012-10-31 10:30 ` [PATCH 3/4] staging:iio: add a callback buffer for in kernel push interface Jonathan Cameron
2012-10-31 14:10   ` Peter Meerwald
2012-11-02 10:53     ` Jonathan Cameron [this message]
2012-10-31 10:30 ` [PATCH 4/4] staging:iio: Proof of concept input driver Jonathan Cameron
2012-10-31 14:40   ` Peter Meerwald
2012-11-02 11:02     ` Jonathan Cameron
2012-11-02 11:06 ` [PATCH 0/4 V6] staging:iio: Add support for multiple buffers (testing required!) Jonathan Cameron
2012-11-10 10:26   ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2012-10-13  9:24 [PATCH 0/4 V5] " Jonathan Cameron
2012-10-13  9:24 ` [PATCH 3/4] staging:iio: add a callback buffer for in kernel push interface Jonathan Cameron
2012-10-17  8:50   ` Lars-Peter Clausen
2012-10-17  8:52     ` Jonathan Cameron
2012-06-30 19:06 [PATCH 0/4 V3] staging:iio: Add support for multiple buffers Jonathan Cameron
2012-06-30 19:06 ` [PATCH 3/4] staging:iio: add a callback buffer for in kernel push interface Jonathan Cameron
2012-05-30 19:36 [PATCH 0/4 V2] staging:iio: Add support for multiple buffers Jonathan Cameron
2012-05-30 19:36 ` [PATCH 3/4] staging:iio: add a callback buffer for in kernel push interface 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=5093A60C.90806@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;
as well as URLs for NNTP newsgroup(s).