From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Sylvain Lemieux <slemieux.tyco@gmail.com>
Cc: Vladimir Zapolskiy <vz@mleia.com>,
linux-input@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Input: lpc32xx-keys - fix invalid error handling of a requested irq
Date: Wed, 7 Dec 2016 17:22:54 -0800 [thread overview]
Message-ID: <20161208012254.GB27638@dtor-ws> (raw)
In-Reply-To: <1481134387.9248.8.camel@localhost>
On Wed, Dec 07, 2016 at 01:13:07PM -0500, Sylvain Lemieux wrote:
> On Mon, 2016-12-05 at 03:47 +0200, Vladimir Zapolskiy 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_keys driver initialization on boot:
> >
> > lpc32xx_keys 40050000.key: failed to get platform irq
> > lpc32xx_keys: probe of 40050000.key failed with error -22
> >
> > Signed-off-by: Vladimir Zapolskiy <vz@mleia.com>
> > ---
> > drivers/input/keyboard/lpc32xx-keys.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> Cosmetic - please update the subject line when doing the commit:
> replace " -" by ":" after lpc32xx-keys
>
> Acked-by: Sylvain Lemieux <slemieux.tyco@gmail.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2016-12-08 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 1:47 [PATCH] Input: lpc32xx-keys - fix invalid error handling of a requested irq Vladimir Zapolskiy
2016-12-07 18:13 ` Sylvain Lemieux
2016-12-07 18:46 ` Dmitry Torokhov
2016-12-07 18:51 ` Sylvain Lemieux
2016-12-08 1:22 ` Dmitry Torokhov [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=20161208012254.GB27638@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=slemieux.tyco@gmail.com \
--cc=vz@mleia.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).