From: Jonathan Cameron <jic23@kernel.org>
To: anish kumar <anish198519851985@gmail.com>
Cc: jic23@cam.ac.uk, linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Documentation change for inkern interface.
Date: Thu, 13 Sep 2012 21:12:41 +0100 [thread overview]
Message-ID: <50523E39.5080708@kernel.org> (raw)
In-Reply-To: <1347133337-7795-1-git-send-email-anish198519851985@gmail.com>
On 09/08/2012 08:42 PM, anish kumar wrote:
> From: anish kumar <anish198519851985@gmail.com>
>
> This commit- 314be14bb renamed the _st_ functions to loose the bit
> that was meant for staging version but forgot to change
> the documentation which still have _st_ sprinkled in some of the
> places.
>
> Signed-off-by: anish kumar <anish198519851985@gmail.com>
merge to togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
> ---
> drivers/staging/iio/Documentation/inkernel.txt | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/iio/Documentation/inkernel.txt b/drivers/staging/iio/Documentation/inkernel.txt
> index a05823e..ab52840 100644
> --- a/drivers/staging/iio/Documentation/inkernel.txt
> +++ b/drivers/staging/iio/Documentation/inkernel.txt
> @@ -48,11 +48,11 @@ There are then a number of functions that can be used to get information
> about this channel such as it's current reading.
>
> e.g.
> -iio_st_read_channel_raw() - get a reading
> -iio_st_read_channel_type() - get the type of channel
> +iio_read_channel_raw() - get a reading
> +iio_get_channel_type() - get the type of channel
>
> There is also provision for retrieving all of the channels associated
> with a given consumer. This is useful for generic drivers such as
> iio_hwmon where the number and naming of channels is not known by the
> -consumer driver. To do this, use iio_st_channel_get_all.
> +consumer driver. To do this, use iio_channel_get_all.
>
>
prev parent reply other threads:[~2012-09-13 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 19:42 [PATCH] iio: Documentation change for inkern interface anish kumar
2012-09-13 20:12 ` 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=50523E39.5080708@kernel.org \
--to=jic23@kernel.org \
--cc=anish198519851985@gmail.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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