From: Jonathan Cameron <jic23@kernel.org>
To: Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 3/3] iio: cleanup buffer.h comments
Date: Tue, 03 Jul 2012 18:30:00 +0100 [thread overview]
Message-ID: <4FF32C18.1050907@kernel.org> (raw)
In-Reply-To: <1341096463-13789-3-git-send-email-pmeerw@pmeerw.net>
On 06/30/2012 11:47 PM, Peter Meerwald wrote:
> Signed-off-by: Peter Meerwald <pmeerw@pmeerw.net>
merged thanks.
> ---
> include/linux/iio/buffer.h | 17 ++++++++++-------
> 1 file changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/include/linux/iio/buffer.h b/include/linux/iio/buffer.h
> index ad4fb1a..2a2b6b4 100644
> --- a/include/linux/iio/buffer.h
> +++ b/include/linux/iio/buffer.h
> @@ -85,7 +85,7 @@ struct iio_buffer {
>
> /**
> * iio_buffer_init() - Initialize the buffer structure
> - * @buffer: buffer to be initialized
> + * @buffer: buffer to be initialized
> **/
> void iio_buffer_init(struct iio_buffer *buffer);
>
> @@ -107,8 +107,9 @@ int iio_scan_mask_query(struct iio_dev *indio_dev,
>
> /**
> * iio_scan_mask_set() - set particular bit in the scan mask
> - * @buffer: the buffer whose scan mask we are interested in
> - * @bit: the bit to be set.
> + * @indio_dev IIO device structure
> + * @buffer: the buffer whose scan mask we are interested in
> + * @bit: the bit to be set.
> **/
> int iio_scan_mask_set(struct iio_dev *indio_dev,
> struct iio_buffer *buffer, int bit);
> @@ -116,8 +117,8 @@ int iio_scan_mask_set(struct iio_dev *indio_dev,
> /**
> * iio_push_to_buffer() - push to a registered buffer.
> * @buffer: IIO buffer structure for device
> - * @scan: Full scan.
> - * @timestamp:
> + * @data: the data to push to the buffer
> + * @timestamp: timestamp to associate with the data
> */
> int iio_push_to_buffer(struct iio_buffer *buffer, unsigned char *data,
> s64 timestamp);
> @@ -126,7 +127,9 @@ int iio_update_demux(struct iio_dev *indio_dev);
>
> /**
> * iio_buffer_register() - register the buffer with IIO core
> - * @indio_dev: device with the buffer to be registered
> + * @indio_dev: device with the buffer to be registered
> + * @channels: the channel descriptions used to construct buffer
> + * @num_channels: the number of channels
> **/
> int iio_buffer_register(struct iio_dev *indio_dev,
> const struct iio_chan_spec *channels,
> @@ -134,7 +137,7 @@ int iio_buffer_register(struct iio_dev *indio_dev,
>
> /**
> * iio_buffer_unregister() - unregister the buffer from IIO core
> - * @indio_dev: the device with the buffer to be unregistered
> + * @indio_dev: the device with the buffer to be unregistered
> **/
> void iio_buffer_unregister(struct iio_dev *indio_dev);
>
>
next prev parent reply other threads:[~2012-07-03 17:30 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
2012-06-30 22:47 ` [PATCH 3/3] iio: cleanup buffer.h comments Peter Meerwald
2012-07-03 17:30 ` Jonathan Cameron [this message]
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=4FF32C18.1050907@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).