From: Jonathan Cameron <jic23@cam.ac.uk>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 6/6] iio: iio/events.h typos
Date: Fri, 15 Jun 2012 13:43:59 +0100 [thread overview]
Message-ID: <4FDB2E0F.4030904@cam.ac.uk> (raw)
In-Reply-To: <1339714260-8361-6-git-send-email-pmeerw@pmeerw.net>
You haven't signed off on this...
Other than the fact that typo's is rather generous for whole
missing words I'm happy with this ;)
Thanks,
Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
> include/linux/iio/events.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/iio/events.h b/include/linux/iio/events.h
> index b5acbf9..13ce220 100644
> --- a/include/linux/iio/events.h
> +++ b/include/linux/iio/events.h
> @@ -46,7 +46,7 @@ enum iio_event_direction {
> * @diff: Whether the event is for an differential channel or not.
> * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
> * @direction: Direction of the event. One of enum iio_event_direction.
> - * @type: Type of the event. Should be one enum iio_event_type.
> + * @type: Type of the event. Should be one of enum iio_event_type.
> * @chan: Channel number for non-differential channels.
> * @chan1: First channel number for differential channels.
> * @chan2: Second channel number for differential channels.
> @@ -69,7 +69,7 @@ enum iio_event_direction {
> * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
> * @number: Channel number.
> * @modifier: Modifier for the channel. Should be one of enum iio_modifier.
> - * @type: Type of the event. Should be one enum iio_event_type.
> + * @type: Type of the event. Should be one of enum iio_event_type.
> * @direction: Direction of the event. One of enum iio_event_direction.
> */
>
> @@ -81,7 +81,7 @@ enum iio_event_direction {
> * IIO_UNMOD_EVENT_CODE() - create event identifier for unmodified channels
> * @chan_type: Type of the channel. Should be one of enum iio_chan_type.
> * @number: Channel number.
> - * @type: Type of the event. Should be one enum iio_event_type.
> + * @type: Type of the event. Should be one of enum iio_event_type.
> * @direction: Direction of the event. One of enum iio_event_direction.
> */
>
next prev parent reply other threads:[~2012-06-15 12:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 22:50 [PATCH 1/6] iio: sysfs-bus-iio typo Peter Meerwald
2012-06-14 22:50 ` [PATCH 2/6] iio: cleanup sysfs-bus-iio-light-lm3533-als Peter Meerwald
2012-06-15 12:48 ` Jonathan Cameron
2012-06-14 22:50 ` [PATCH 3/6] iio: iio/machine.h typo Peter Meerwald
2012-06-15 12:46 ` Jonathan Cameron
2012-06-14 22:50 ` [PATCH 4/6] iio: add IIO_ALTVOLTAGE to iio_event_monitor example Peter Meerwald
2012-06-15 12:46 ` Jonathan Cameron
2012-06-14 22:50 ` [PATCH 5/6] iio staging: typos Peter Meerwald
2012-06-15 12:45 ` Jonathan Cameron
2012-06-14 22:51 ` [PATCH 6/6] iio: iio/events.h typos Peter Meerwald
2012-06-15 12:43 ` Jonathan Cameron [this message]
2012-06-15 12:48 ` [PATCH 1/6] iio: sysfs-bus-iio typo Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2012-06-15 17:25 Peter Meerwald
2012-06-15 17:25 ` [PATCH 6/6] iio: iio/events.h typos Peter Meerwald
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=4FDB2E0F.4030904@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.