linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@cam.ac.uk>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 01/11] staging:iio:ad7298: Do not return error code in interrupt handler
Date: Sat, 07 Jul 2012 16:47:19 +0100	[thread overview]
Message-ID: <4FF85A07.3030704@kernel.org> (raw)
In-Reply-To: <1341418173-3217-1-git-send-email-lars@metafoo.de>

On 07/04/2012 05:09 PM, Lars-Peter Clausen wrote:
> The interrupt handler should only ever return one of the three irqreturn_t
> constants and not an error code. Also make sure to always call
> iio_trigger_notify_done before leaving the trigger handler.
> 
merged all. Thanks.
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
>  drivers/staging/iio/adc/ad7298_ring.c |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/iio/adc/ad7298_ring.c b/drivers/staging/iio/adc/ad7298_ring.c
> index cd3e9cb..fd1d855 100644
> --- a/drivers/staging/iio/adc/ad7298_ring.c
> +++ b/drivers/staging/iio/adc/ad7298_ring.c
> @@ -82,7 +82,7 @@ static irqreturn_t ad7298_trigger_handler(int irq, void *p)
>  
>  	b_sent = spi_sync(st->spi, &st->ring_msg);
>  	if (b_sent)
> -		return b_sent;
> +		goto done;
>  
>  	if (indio_dev->scan_timestamp) {
>  		time_ns = iio_get_time_ns();
> @@ -95,6 +95,8 @@ static irqreturn_t ad7298_trigger_handler(int irq, void *p)
>  		buf[i] = be16_to_cpu(st->rx_buf[i]);
>  
>  	indio_dev->buffer->access->store_to(ring, (u8 *)buf, time_ns);
> +
> +done:
>  	iio_trigger_notify_done(indio_dev->trig);
>  
>  	return IRQ_HANDLED;
> 

      parent reply	other threads:[~2012-07-07 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-04 16:09 [PATCH 01/11] staging:iio:ad7298: Do not return error code in interrupt handler Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 02/11] staging:iio:adt7310: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 03/11] staging:iio:dummy driver: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 04/11] staging:iio:ad799x: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 05/11] staging:iio:ad7476: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 06/11] staging:iio:ad7887: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 07/11] staging:iio:max1363: " Lars-Peter Clausen
2012-07-09 21:36   ` Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 08/11] staging:iio:lis3l02dq: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 09/11] staging:iio:accel:adis16xxx: Do not return error code in the " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 10/11] staging:iio:adis16260: " Lars-Peter Clausen
2012-07-04 16:09 ` [PATCH 11/11] staging:iio:adis16400: " Lars-Peter Clausen
2012-07-07 15:47 ` 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=4FF85A07.3030704@kernel.org \
    --to=jic23@kernel.org \
    --cc=jic23@cam.ac.uk \
    --cc=lars@metafoo.de \
    --cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).