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 RESEND v2 1/4] iio: fix typos in iio.h
Date: Tue, 12 Jun 2012 14:37:36 +0100	[thread overview]
Message-ID: <4FD74620.9000205@kernel.org> (raw)
In-Reply-To: <1339507788-2931-1-git-send-email-pmeerw@pmeerw.net>

On 6/12/2012 2:29 PM, Peter Meerwald wrote:
> From: Peter Meerwald<p.meerwald@bct-electronic.com>
>
> v2:
> * "used in in-kernel" (Jonathan Cameron)
>
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
>   include/linux/iio/iio.h |    6 +++---
>   1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 944c635..9d9b55a 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -131,7 +131,7 @@ struct iio_chan_spec_ext_info {
>
>   /**
>    * struct iio_enum - Enum channel info attribute
> - * items: A array of strings.
> + * items: An array of strings.
>    * num_items: Length of the item array.
>    * set: Set callback function, may be NULL.
>    * get: Get callback function, may be NULL.
> @@ -218,7 +218,7 @@ ssize_t iio_enum_write(struct iio_dev *indio_dev,
>    * @extend_name:	Allows labeling of channel attributes with an
>    *			informative name. Note this has no effect codes etc,
>    *			unlike modifiers.
> - * @datasheet_name:	A name used in in kernel mapping of channels. It should
> + * @datasheet_name:	A name used in in-kernel mapping of channels. It should
>    *			correspond to the first name that the channel is referred
>    *			to by in the datasheet (e.g. IND), or the nearest
>    *			possible compound name (e.g. IND-INC).
> @@ -393,7 +393,7 @@ struct iio_buffer_setup_ops {
>    * @trig:		[INTERN] current device trigger (buffer modes)
>    * @pollfunc:		[DRIVER] function run on trigger being received
>    * @channels:		[DRIVER] channel specification structure table
> - * @num_channels:	[DRIVER] number of chanels specified in @channels.
> + * @num_channels:	[DRIVER] number of channels specified in @channels.
>    * @channel_attr_list:	[INTERN] keep track of automatically created channel
>    *			attributes
>    * @chan_attr_group:	[INTERN] group for all attrs in base directory


  reply	other threads:[~2012-06-12 13:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 13:29 [PATCH RESEND v2 1/4] iio: fix typos in iio.h Peter Meerwald
2012-06-12 13:37 ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-12 13:38 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=4FD74620.9000205@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).