From: Jonathan Cameron <jic23@kernel.org>
To: Nuno Sa <nuno.sa@analog.com>
Cc: <linux-iio@vger.kernel.org>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Alexandru Ardelean <ardeleanalex@gmail.com>
Subject: Re: [PATCH v2 2/9] iio: adis16400: do not return ints in irq handlers
Date: Sat, 24 Apr 2021 12:00:56 +0100 [thread overview]
Message-ID: <20210424120056.369998d7@jic23-huawei> (raw)
In-Reply-To: <20210422101911.135630-3-nuno.sa@analog.com>
On Thu, 22 Apr 2021 12:19:04 +0200
Nuno Sa <nuno.sa@analog.com> wrote:
> On an IRQ handler we should not return normal error codes as 'irqreturn_t'
> is expected.
>
> Fixes: 5eda3550a3cc1 ("staging:iio:adis16400: Preallocate transfer message")
> Reviewed-by: Alexandru Ardelean <ardeleanalex@gmail.com>
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
Same approach as for previous patch.
Applied to the togreg branch of iio.git and pushed out as testing.
Thanks,
Jonathan
> ---
> drivers/iio/imu/adis16400.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/drivers/iio/imu/adis16400.c b/drivers/iio/imu/adis16400.c
> index 768aa493a1a6..b2f92b55b910 100644
> --- a/drivers/iio/imu/adis16400.c
> +++ b/drivers/iio/imu/adis16400.c
> @@ -645,9 +645,6 @@ static irqreturn_t adis16400_trigger_handler(int irq, void *p)
> void *buffer;
> int ret;
>
> - if (!adis->buffer)
> - return -ENOMEM;
> -
> if (!(st->variant->flags & ADIS16400_NO_BURST) &&
> st->adis.spi->max_speed_hz > ADIS16400_SPI_BURST) {
> st->adis.spi->max_speed_hz = ADIS16400_SPI_BURST;
next prev parent reply other threads:[~2021-04-24 11:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 10:19 [PATCH v2 0/9] Adis IRQ fixes and minor improvements Nuno Sa
2021-04-22 10:19 ` [PATCH v2 1/9] iio: adis_buffer: do not return ints in irq handlers Nuno Sa
2021-04-24 10:59 ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 2/9] iio: adis16400: " Nuno Sa
2021-04-24 11:00 ` Jonathan Cameron [this message]
2021-04-22 10:19 ` [PATCH v2 3/9] iio: adis16475: " Nuno Sa
2021-04-23 6:41 ` Alexandru Ardelean
2021-04-24 11:06 ` Jonathan Cameron
2021-04-26 9:45 ` Sa, Nuno
2021-04-22 10:19 ` [PATCH v2 4/9] iio: adis_buffer: check return value on page change Nuno Sa
2021-04-23 7:14 ` Alexandru Ardelean
2021-04-24 11:07 ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 5/9] iio: adis_buffer: don't push data to buffers on failure Nuno Sa
2021-04-23 7:28 ` Alexandru Ardelean
2021-04-24 11:13 ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 6/9] iio: adis_buffer: update device page after changing it Nuno Sa
2021-04-23 7:32 ` Alexandru Ardelean
2021-04-23 12:20 ` Sa, Nuno
2021-04-23 13:56 ` Alexandru Ardelean
2021-04-24 11:18 ` Jonathan Cameron
2021-04-24 11:19 ` Jonathan Cameron
2021-04-24 11:31 ` Jonathan Cameron
2021-04-26 9:54 ` Sa, Nuno
2021-04-26 9:46 ` Sa, Nuno
2021-04-22 10:19 ` [PATCH v2 7/9] iio: adis: add burst_max_speed_hz variable Nuno Sa
2021-04-23 7:34 ` Alexandru Ardelean
2021-04-24 11:26 ` Jonathan Cameron
2021-04-22 10:19 ` [PATCH v2 8/9] iio: adis16475: do not directly change spi 'max_speed_hz' Nuno Sa
2021-04-23 7:36 ` Alexandru Ardelean
2021-04-22 10:19 ` [PATCH v2 9/9] iio: adis16400: " Nuno Sa
2021-04-23 7:37 ` Alexandru Ardelean
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=20210424120056.369998d7@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=ardeleanalex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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).