linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Hartmut Knaack <knaack.h@gmx.de>,
	Jonathan Cameron <jic23@kernel.org>,
	Cristina Opriceana <cristina.opriceana@gmail.com>
Cc: pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, daniel.baluta@intel.com
Subject: Re: [PATCH 4/6] iio: event: Add missing fields in kernel docs
Date: Mon, 03 Aug 2015 11:05:25 +0200	[thread overview]
Message-ID: <55BF2ED5.60104@metafoo.de> (raw)
In-Reply-To: <55BE72C5.5020900@gmx.de>

On 08/02/2015 09:43 PM, Hartmut Knaack wrote:
> Jonathan Cameron schrieb am 02.08.2015 um 19:33:
>> On 24/07/15 14:21, Cristina Opriceana wrote:
>>> Fix kernel docs warnings by adding the missing fields,
>>> each with its associated description.
>>>
>>> Signed-off-by: Cristina Opriceana <cristina.opriceana@gmail.com>
>> Applied.  Thanks
>>
>> Jonathan
>>> ---
>>>  drivers/iio/industrialio-event.c | 6 ++++++
>>>  1 file changed, 6 insertions(+)
>>>
>>> diff --git a/drivers/iio/industrialio-event.c b/drivers/iio/industrialio-event.c
>>> index 894d813..b2f63f9 100644
>>> --- a/drivers/iio/industrialio-event.c
>>> +++ b/drivers/iio/industrialio-event.c
>>> @@ -32,6 +32,7 @@
>>>   * @dev_attr_list:	list of event interface sysfs attribute
>>>   * @flags:		file operations related flags including busy flag.
>>>   * @group:		event interface sysfs attribute group
>>> + * @read_lock:		lock to protect kfifo read operations
>>>   */
>>>  struct iio_event_interface {
>>>  	wait_queue_head_t	wait;
>>> @@ -75,6 +76,11 @@ EXPORT_SYMBOL(iio_push_event);
>>>  
>>>  /**
>>>   * iio_event_poll() - poll the event queue to find out if it has data
>>> + * @filep:	File structure pointer to identify the device
>>> + * @wait:	Poll table pointer to add the wait queue on
>>> + *
>>> + * Return: (POLLIN | POLLRDNORM) if data is available for reading
>>> + *	   or a negative error code on failure
> 
> This can also return 0 if no data is available.
> 
> Actually, being unsigned int, the intended negative error code won't
> appear - ouch! Any volunteers to address this issue?

Sorry, my fault. It looks like the poll() callback can't return a error. So
if no device is bound we should just return 0.

- Lars


  parent reply	other threads:[~2015-08-03  9:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 13:13 [PATCH 0/6] iio: Fix kernel docs warnings 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
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 [this message]
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=55BF2ED5.60104@metafoo.de \
    --to=lars@metafoo.de \
    --cc=cristina.opriceana@gmail.com \
    --cc=daniel.baluta@intel.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.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;
as well as URLs for NNTP newsgroup(s).