linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: Masanari Iida <standby24x7@gmail.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] staging, iio: Fix typo in iio
Date: Tue, 08 May 2012 13:41:19 +0100	[thread overview]
Message-ID: <4FA9146F.5050802@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D5917714E797B53AE@LIMKCMBX1.ad.analog.com>

On 5/7/2012 8:35 PM, Hennerich, Michael wrote:
> Masanari Iida wrote on 2012-05-07:
>> Correct spelling typo in staging/iio
>>
>> Signed-off-by: Masanari Iida<standby24x7@gmail.com>
> Acked-by: Michael Hennerich<michael.hennerich@analog.com>
Acked-by: Jonathan Cameron <jic23@kernel.org>

Please send to Gregkh@linuxfoundation.org
>> ---
>>   drivers/staging/iio/TODO                      | 2 +-
>>   drivers/staging/iio/gyro/adxrs450.h           | 2 +-
>>   drivers/staging/iio/iio_simple_dummy_buffer.c | 4 ++--
>>   drivers/staging/iio/iio_simple_dummy_events.c | 2 +-
>>   4 files changed, 5 insertions(+), 5 deletions(-)
>> diff --git a/drivers/staging/iio/TODO b/drivers/staging/iio/TODO
>> index d1ad35e..cf3f948 100644
>> --- a/drivers/staging/iio/TODO
>> +++ b/drivers/staging/iio/TODO
>> @@ -67,7 +67,7 @@ e-mailing the normal IIO list (see below).
>>
>>   Documentation
>>   1) Lots of cleanup and expansion.
>> -2) Some device require indvidual docs.
>> +2) Some device require individual docs.
>>
>>   Contact: Jonathan Cameron<jic23@cam.ac.uk>.
>>   Mailing list: linux-iio@vger.kernel.org
>> diff --git a/drivers/staging/iio/gyro/adxrs450.h
>> b/drivers/staging/iio/gyro/adxrs450.h index af0c870..f8cf21f 100644 ---
>> a/drivers/staging/iio/gyro/adxrs450.h +++
>> b/drivers/staging/iio/gyro/adxrs450.h @@ -49,7 +49,7 @@ enum {
>>    * @us:                      actual spi_device
>>    * @buf_lock:                mutex to protect tx and rx
>>    * @tx:                      transmit buffer
>> - * @rx:                      recieve buffer
>> + * @rx:                      receive buffer
>>    **/
>>   struct adxrs450_state {
>>        struct spi_device       *us;
>> diff --git a/drivers/staging/iio/iio_simple_dummy_buffer.c
>> b/drivers/staging/iio/iio_simple_dummy_buffer.c index bb4daf7..389c18a
>> 100644 --- a/drivers/staging/iio/iio_simple_dummy_buffer.c +++
>> b/drivers/staging/iio/iio_simple_dummy_buffer.c @@ -37,7 +37,7 @@ static
>> const s16 fakedata[] = {
>>    * @irq: the interrupt number
>>    * @p: private data - always a pointer to the poll func.
>>    *
>> - * This is the guts of buffered capture. On a trigger event occuring,
>> + * This is the guts of buffered capture. On a trigger event occurring,
>>    * if the pollfunc is attached then this handler is called as a
>>    threaded * interrupt (and hence may sleep). It is responsible for
>>    grabbing data * from the device and pushing it into the associated
>>    buffer.
>> @@ -64,7 +64,7 @@ static irqreturn_t iio_simple_dummy_trigger_h(int
>> irq, void *p)
>>                 *   up a fast read.  The capture will consist of all of them.           *
>>   Hence we just call the grab data function and fill the                *   buffer
>>   without processing.
>> -              * sofware scans: can be considered to be random access
>> +              * software scans: can be considered to be random access
>>                 *   so efficient reading is just a case of minimal bus
>>                 *   transactions.
>>                 * software culled hardware scans:
>> diff --git a/drivers/staging/iio/iio_simple_dummy_events.c
>> b/drivers/staging/iio/iio_simple_dummy_events.c index 449c7a5..368317b
>> 100644 --- a/drivers/staging/iio/iio_simple_dummy_events.c +++
>> b/drivers/staging/iio/iio_simple_dummy_events.c @@ -122,7 +122,7 @@ int
>> iio_simple_dummy_write_event_value(struct iio_dev *indio_dev,
>>    * @private: pointer to device instance state.
>>    *
>>    * This handler is responsible for querying the device to find out
>> what
>> - * event occured and for then pushing that event towards userspace.
>> + * event occurred and for then pushing that event towards userspace.
>>    * Here only one event occurs so we push that directly on with locally
>>    * grabbed timestamp.
>>    */
> Greetings,
> Michael
>
> --
> Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
> Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
> Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin, Margaret Seif
>
>
>
> --
> 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


  reply	other threads:[~2012-05-08 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 16:18 [PATCH] staging, iio: Fix typo in iio Masanari Iida
2012-05-07 19:35 ` Hennerich, Michael
2012-05-08 12:41   ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-22 11:23 [PATCH] staging: " Masanari Iida
2014-04-22 21:41 ` Randy Dunlap
2014-04-23 20:45   ` 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=4FA9146F.5050802@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=device-drivers-devel@blackfin.uclinux.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=standby24x7@gmail.com \
    /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).