From: Hartmut Knaack <knaack.h@gmx.de>
To: Jonathan Cameron <jic23@kernel.org>,
Cristina Opriceana <cristina.opriceana@gmail.com>
Cc: lars@metafoo.de, pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, daniel.baluta@intel.com
Subject: Re: [PATCH 2/6] iio: buffer: Fix kernel docs warnings
Date: Sun, 02 Aug 2015 21:46:29 +0200 [thread overview]
Message-ID: <55BE7395.1090503@gmx.de> (raw)
In-Reply-To: <55BE7031.5090009@gmx.de>
Hartmut Knaack schrieb am 02.08.2015 um 21:32:
> Jonathan Cameron schrieb am 02.08.2015 um 19:27:
>> On 24/07/15 14:18, Cristina Opriceana wrote:
>>> Fix kernel docs for structures and functions in order to
>>> remove some warnings when the documentation gets generated.
>>>
>>> Signed-off-by: Cristina Opriceana <cristina.opriceana@gmail.com>
>> Applied with another typo fixed up.
>
> Hi,
> I'm afraid there is some information missing.
>
>>> ---
>>> drivers/iio/industrialio-buffer.c | 15 ++++++++++++++-
>>> 1 file changed, 14 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/iio/industrialio-buffer.c b/drivers/iio/industrialio-buffer.c
>>> index b13f941..a671953 100644
>>> --- a/drivers/iio/industrialio-buffer.c
>>> +++ b/drivers/iio/industrialio-buffer.c
>>> @@ -91,9 +91,16 @@ static bool iio_buffer_ready(struct iio_dev *indio_dev, struct iio_buffer *buf,
>>>
>>> /**
>>> * iio_buffer_read_first_n_outer() - chrdev read for buffer access
>>> + * @filp: File structure pointer for the char device
>>> + * @buf: Destination buffer for iio buffer read
>>> + * @n: First n bytes to read
>>> + * @f_ps: Long offset provided by the user as a seek position
>>> *
>>> * This function relies on all buffer implementations having an
>>> * iio_buffer as their first element.
>>> + *
>>> + * Return: negative values corresponding to error codes or ret != 0
>>> + * for ending the reading activity
>
> This may also return 0. Would it be wrong to state that if the return
> value is not negative, then it will indicate the amount of data read?
>
>>> **/
>>> ssize_t iio_buffer_read_first_n_outer(struct file *filp, char __user *buf,
>>> size_t n, loff_t *f_ps)
>>> @@ -143,6 +150,12 @@ ssize_t iio_buffer_read_first_n_outer(struct file *filp, char __user *buf,
>>>
>>> /**
>>> * iio_buffer_poll() - poll the buffer to find out if it has data
>>> + * @filp: File structure poiner for device access
>> pointer
>>> + * @wait: Poll table structure pointer for which the driver adds
>>> + * a wait queue
>>> + *
>>> + * Return: (POLLIN | POLLRDNORM) if data is available for reading
>>> + * or 0 for other cases
>
> This can also return -ENODEV.
On second thought however, it may return anything, given it is unsigned int.
Any volunteers?
>
>>> */
>>> unsigned int iio_buffer_poll(struct file *filp,
>>> struct poll_table_struct *wait)
>>> @@ -1136,7 +1149,7 @@ int iio_scan_mask_query(struct iio_dev *indio_dev,
>>> EXPORT_SYMBOL_GPL(iio_scan_mask_query);
>>>
>>> /**
>>> - * struct iio_demux_table() - table describing demux memcpy ops
>>> + * struct iio_demux_table - table describing demux memcpy ops
>>> * @from: index to copy from
>>> * @to: index to copy to
>>> * @length: how many bytes to copy
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-08-02 19:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 13:13 [PATCH 0/6] iio: " Cristina Opriceana
2015-07-24 13:16 ` [PATCH 1/6] iio: core: Add function params for kernel docs Cristina Opriceana
2015-08-02 17:24 ` Jonathan Cameron
2015-07-24 13:18 ` [PATCH 2/6] iio: buffer: Fix kernel docs warnings Cristina Opriceana
2015-08-02 17:27 ` Jonathan Cameron
2015-08-02 19:32 ` Hartmut Knaack
2015-08-02 19:46 ` Hartmut Knaack [this message]
2015-08-03 10:45 ` Cristina Georgiana Opriceana
2015-07-24 13:20 ` [PATCH 3/6] iio: trigger: Add missing fields in kernel docs Cristina Opriceana
2015-08-02 17:32 ` Jonathan Cameron
2015-08-06 11:59 ` Cristina Georgiana Opriceana
2015-07-24 13:21 ` [PATCH 4/6] iio: event: " Cristina Opriceana
2015-08-02 17:33 ` Jonathan Cameron
2015-08-02 19:43 ` Hartmut Knaack
2015-08-03 9:00 ` Cristina Georgiana Opriceana
2015-08-03 9:05 ` Lars-Peter Clausen
2015-07-24 13:23 ` [PATCH 5/6] include: linux: iio: Fix function parameter name in kernel doc Cristina Opriceana
2015-08-02 17:34 ` Jonathan Cameron
2015-07-24 13:26 ` [PATCH 6/6] include: linux: iio: Add missing kernel doc field Cristina Opriceana
2015-08-02 17:37 ` 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=55BE7395.1090503@gmx.de \
--to=knaack.h@gmx.de \
--cc=cristina.opriceana@gmail.com \
--cc=daniel.baluta@intel.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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
Powered by JetHome