From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/3] iio: another typo in comment
Date: Tue, 03 Jul 2012 18:27:25 +0100 [thread overview]
Message-ID: <4FF32B7D.40303@kernel.org> (raw)
In-Reply-To: <1341096463-13789-2-git-send-email-pmeerw@pmeerw.net>
On 06/30/2012 11:47 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
> ---
> include/linux/iio/iio.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 2afbb6f..72f8851 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -220,7 +220,7 @@ ssize_t iio_enum_write(struct iio_dev *indio_dev,
> * unlike modifiers.
> * @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
> + * to in the datasheet (e.g. IND), or the nearest
Nope. The original is correct English. Referred to implies some sort of
transference, referred to by implies that this name is used.
There might be a better way of putting it, but it's not that uncommon a
usage.
> * possible compound name (e.g. IND-INC).
> * @modified: Does a modifier apply to this channel. What these are
> * depends on the channel type. Modifier is set in
>
next prev parent reply other threads:[~2012-07-03 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 22:47 [PATCH 1/3] iio staging: missing newline in printf Peter Meerwald
2012-06-30 22:47 ` [PATCH 2/3] iio: another typo in comment Peter Meerwald
2012-07-03 17:27 ` Jonathan Cameron [this message]
2012-06-30 22:47 ` [PATCH 3/3] iio: cleanup buffer.h comments Peter Meerwald
2012-07-03 17:30 ` Jonathan Cameron
2012-07-03 17:30 ` [PATCH 1/3] iio staging: missing newline in printf 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=4FF32B7D.40303@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).