From: Jonathan Cameron <jic23@kernel.org>
To: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Cc: linux-iio@vger.kernel.org, trivial@kernel.org,
Jonathan Cameron <jic23@cam.ac.uk>
Subject: Re: [PATCH] iio: Fix some comments
Date: Thu, 27 Dec 2012 11:22:54 +0000 [thread overview]
Message-ID: <50DC2F8E.3010805@kernel.org> (raw)
In-Reply-To: <1355939791-18814-1-git-send-email-alexander.stein@informatik.tu-chemnitz.de>
On 12/19/2012 05:56 PM, Alexander Stein wrote:
> Signed-off-by: Alexander Stein <alexander.stein@informatik.tu-chemnitz.de>
Thanks,
Added to togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
I really ought to do something about moving this out of staging if
people still find it useful/informative.
hmm.
Jonathan
> ---
> drivers/staging/iio/iio_simple_dummy.c | 4 ++--
> drivers/staging/iio/iio_simple_dummy_buffer.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/iio_simple_dummy.c b/drivers/staging/iio/iio_simple_dummy.c
> index a865adf..aee76c7 100644
> --- a/drivers/staging/iio/iio_simple_dummy.c
> +++ b/drivers/staging/iio/iio_simple_dummy.c
> @@ -54,7 +54,7 @@ struct iio_dummy_accel_calibscale {
> static const struct iio_dummy_accel_calibscale dummy_scales[] = {
> { 0, 100, 0x8 }, /* 0.000100 */
> { 0, 133, 0x7 }, /* 0.000133 */
> - { 733, 13, 0x9 }, /* 733.00013 */
> + { 733, 13, 0x9 }, /* 733.000013 */
> };
>
> /*
> @@ -284,7 +284,7 @@ static int iio_dummy_read_raw(struct iio_dev *indio_dev,
> /**
> * iio_dummy_write_raw() - data write function.
> * @indio_dev: the struct iio_dev associated with this device instance
> - * @chan: the channel whose data is to be read
> + * @chan: the channel whose data is to be written
> * @val: first element of value to set (typically INT)
> * @val2: second element of value to set (typically MICRO)
> * @mask: what we actually want to write. 0 is the channel, everything else
> diff --git a/drivers/staging/iio/iio_simple_dummy_buffer.c b/drivers/staging/iio/iio_simple_dummy_buffer.c
> index dee16f0..72f400c 100644
> --- a/drivers/staging/iio/iio_simple_dummy_buffer.c
> +++ b/drivers/staging/iio/iio_simple_dummy_buffer.c
> @@ -155,7 +155,7 @@ int iio_simple_dummy_configure_buffer(struct iio_dev *indio_dev,
> * occurs, this function is run. Typically this grabs data
> * from the device.
> *
> - * NULL for the top half. This is normally implemented only if we
> + * NULL for the bottom half. This is normally implemented only if we
> * either want to ping a capture now pin (no sleeping) or grab
> * a timestamp as close as possible to a data ready trigger firing.
> *
>
prev parent reply other threads:[~2012-12-27 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 17:56 [PATCH] iio: Fix some comments Alexander Stein
2012-12-27 11:22 ` Jonathan Cameron [this message]
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=50DC2F8E.3010805@kernel.org \
--to=jic23@kernel.org \
--cc=alexander.stein@informatik.tu-chemnitz.de \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=trivial@kernel.org \
/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).