From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/4] iio: clarify channel and indexed in struct iio_chan_spec
Date: Tue, 12 Jun 2012 13:55:59 +0100 [thread overview]
Message-ID: <4FD73C5F.8060503@kernel.org> (raw)
In-Reply-To: <1339504946-16171-2-git-send-email-pmeerw@pmeerw.net>
On 6/12/2012 1:42 PM, Peter Meerwald wrote:
> From: Peter Meerwald<p.meerwald@bct-electronic.com>
>
> Signed-off-by: Peter Meerwald<pmeerw@pmeerw.net>
Acked-by: Jonathan Cameron <jic23@kernel.org>
>
> ---
> include/linux/iio/iio.h | 7 +++----
> 1 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 9d9b55a..44b9660 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -196,7 +196,7 @@ ssize_t iio_enum_write(struct iio_dev *indio_dev,
> /**
> * struct iio_chan_spec - specification of a single channel
> * @type: What type of measurement is the channel making.
> - * @channel: What number or name do we wish to assign the channel.
> + * @channel: What number do we wish to assign the channel.
> * @channel2: If there is a second number for a differential
> * channel then this is it. If modified is set then the
> * value here specifies the modifier.
> @@ -227,9 +227,8 @@ ssize_t iio_enum_write(struct iio_dev *indio_dev,
> * channel2. Examples are IIO_MOD_X for axial sensors about
> * the 'x' axis.
> * @indexed: Specify the channel has a numerical index. If not,
> - * the value in channel will be suppressed for attribute
> - * but not for event codes. Typically set it to 0 when
> - * the index is false.
> + * the channel index number will be suppressed for sysfs
> + * attributes but not for event codes.
> * @differential: Channel is differential.
> */
> struct iio_chan_spec {
next prev parent reply other threads:[~2012-06-12 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 12:42 [PATCH RESEND 1/4] iio: fix typos in iio.h Peter Meerwald
2012-06-12 12:42 ` [PATCH 2/4] iio: clarify channel and indexed in struct iio_chan_spec Peter Meerwald
2012-06-12 12:55 ` Jonathan Cameron [this message]
2012-06-12 12:42 ` [PATCH RESEND 3/4] iio: mark struct iio_enum elements with @ in comment Peter Meerwald
2012-06-12 12:56 ` Jonathan Cameron
2012-06-12 12:42 ` [PATCH 4/4] iio: cleanup iio/iio.h Peter Meerwald
2012-06-12 12:58 ` Jonathan Cameron
2012-06-12 12:55 ` [PATCH RESEND 1/4] iio: fix typos in iio.h Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2012-06-12 13:38 [PATCH RESEND v2 " Peter Meerwald
2012-06-12 13:38 ` [PATCH 2/4] iio: clarify channel and indexed in struct iio_chan_spec 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=4FD73C5F.8060503@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).