From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org, Roland Stigge <stigge@antcom.de>
Subject: Re: [PATCH 1/2] staging:iio:lpc32xx_adc: Fix IRQ check
Date: Thu, 17 Oct 2013 23:13:26 +0100 [thread overview]
Message-ID: <52606106.7010904@kernel.org> (raw)
In-Reply-To: <1381956352-13311-1-git-send-email-lars@metafoo.de>
On 10/16/13 21:45, Lars-Peter Clausen wrote:
> The test in the lpc32xx_adc driver which checks whether the IRQ number returned
> by platform_get_irq() has multiple problems. It accepts 0 even though this is an
> invalid IRQ. It also rejects IRQ numbers that are larger or equal than NR_IRQS.
> First of all drivers should never need to reference NR_IRQS and secondly with
> CONFIG_SPARSE_IRQ NR_IRQS is not the upper limit, so the check might reject
> valid IRQ numbers. This patch modifies the check to only test against less or
> equal to 0.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Cc: Roland Stigge <stigge@antcom.de>
Applied to the togreg branch of iio.git
Thanks,
Jonathan
> ---
> drivers/staging/iio/adc/lpc32xx_adc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/adc/lpc32xx_adc.c b/drivers/staging/iio/adc/lpc32xx_adc.c
> index ce7ff3e..ef0a21d 100644
> --- a/drivers/staging/iio/adc/lpc32xx_adc.c
> +++ b/drivers/staging/iio/adc/lpc32xx_adc.c
> @@ -160,7 +160,7 @@ static int lpc32xx_adc_probe(struct platform_device *pdev)
> }
>
> irq = platform_get_irq(pdev, 0);
> - if ((irq < 0) || (irq >= NR_IRQS)) {
> + if (irq <= 0) {
> dev_err(&pdev->dev, "failed getting interrupt resource\n");
> return -EINVAL;
> }
>
prev parent reply other threads:[~2013-10-17 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 20:45 [PATCH 1/2] staging:iio:lpc32xx_adc: Fix IRQ check Lars-Peter Clausen
2013-10-16 20:45 ` [PATCH 2/2] staging:iio:spear_adc: " Lars-Peter Clausen
2013-10-17 22:14 ` Jonathan Cameron
2013-10-17 22:13 ` 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=52606106.7010904@kernel.org \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=stigge@antcom.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.