linux-kernel - Re: [PATCH] staging, iio: Fix typo in iio

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 08 May 2012 13:41:19 +0100
From:	Jonathan Cameron <jic23@....ac.uk>
To:	"Hennerich, Michael" <Michael.Hennerich@...log.com>
CC:	Masanari Iida <standby24x7@...il.com>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"device-drivers-devel@...ckfin.uclinux.org" 
	<device-drivers-devel@...ckfin.uclinux.org>
Subject: Re: [PATCH] staging, iio: Fix typo in iio

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@...il.com>
> Acked-by: Michael Hennerich<michael.hennerich@...log.com>
Acked-by: Jonathan Cameron <jic23@...nel.org>

Please send to Gregkh@...uxfoundation.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@....ac.uk>.
>>   Mailing list: linux-iio@...r.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@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/