From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: lpc32xx: fix invalid error handling of a requested irq
Date: Tue, 3 Jan 2017 10:12:59 +0100 [thread overview]
Message-ID: <20170103101259.0ec123df@bbrezillon> (raw)
In-Reply-To: <20161205014710.2015-1-vz@mleia.com>
Hi Vladimir
On Mon, 5 Dec 2016 03:47:10 +0200
Vladimir Zapolskiy <vz@mleia.com> wrote:
> Semantics of NR_IRQS is different on machines with SPARSE_IRQ option
> disabled or enabled, in the latter case IRQs are allocated starting
> at least from the value specified by NR_IRQS and going upwards, so
> the check of (irq >= NR_IRQ) to decide about an error code returned by
> platform_get_irq() is completely invalid, don't attempt to overrule
> irq subsystem in the driver.
>
> The change fixes LPC32xx NAND MLC driver initialization on boot.
Do you need to backport this fix to stable releases? If that's the
case, I'll add the Cc: stable tag when applying.
Thanks,
Boris
>
> Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
> ---
> drivers/mtd/nand/lpc32xx_mlc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/lpc32xx_mlc.c b/drivers/mtd/nand/lpc32xx_mlc.c
> index 8523881..bc6e49a 100644
> --- a/drivers/mtd/nand/lpc32xx_mlc.c
> +++ b/drivers/mtd/nand/lpc32xx_mlc.c
> @@ -776,7 +776,7 @@ static int lpc32xx_nand_probe(struct platform_device *pdev)
> init_completion(&host->comp_controller);
>
> host->irq = platform_get_irq(pdev, 0);
> - if ((host->irq < 0) || (host->irq >= NR_IRQS)) {
> + if (host->irq < 0) {
> dev_err(&pdev->dev, "failed to get platform irq\n");
> res = -EINVAL;
> goto err_exit3;
next prev parent reply other threads:[~2017-01-03 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 1:47 [PATCH] mtd: nand: lpc32xx: fix invalid error handling of a requested irq Vladimir Zapolskiy
2016-12-07 18:09 ` Sylvain Lemieux
2017-01-03 9:12 ` Boris Brezillon [this message]
2017-01-03 10:16 ` Vladimir Zapolskiy
2017-01-03 10:47 ` Boris Brezillon
2017-01-05 17:58 ` Brian Norris
2017-01-05 18:19 ` Vladimir Zapolskiy
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=20170103101259.0ec123df@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).