mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Arvind Yadav <arvind.yadav.cs@gmail.com>
Cc: maxime.ripard@free-electrons.com, wens@csie.org,
	mcuos.com@gmail.com, linux@roeck-us.net, linux@armlinux.org.uk,
	lee.jones@linaro.org, linux-kernel@vger.kernel.org,
	linux-input@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/10 v3] Input: ep93xx_keypad: Fix platform_get_irq's error checking
Date: Sat, 18 Nov 2017 10:30:29 -0800	[thread overview]
Message-ID: <20171118183029.zooxomhrejzatuvd@dtor-ws> (raw)
In-Reply-To: <a9a25cd5775ba4c76d47e8b66934e470f58d9e72.1510999558.git.arvind.yadav.cs@gmail.com>

On Sat, Nov 18, 2017 at 04:25:08PM +0530, Arvind Yadav wrote:
> The platform_get_irq() function returns negative if an error occurs.
> zero or positive number on success. platform_get_irq() error checking
> for zero is not correct.
> 
> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
> ---
> changes in v2:
>                Return keypad->irq insted of -ENXIO.
> changes in v3 :
>                Add failure case '<= 0' instead of '< 0'. IRQ0 is not valid.
> 
>  drivers/input/keyboard/ep93xx_keypad.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/input/keyboard/ep93xx_keypad.c b/drivers/input/keyboard/ep93xx_keypad.c
> index f77b295..01788a7 100644
> --- a/drivers/input/keyboard/ep93xx_keypad.c
> +++ b/drivers/input/keyboard/ep93xx_keypad.c
> @@ -257,8 +257,8 @@ static int ep93xx_keypad_probe(struct platform_device *pdev)
>  	}
>  
>  	keypad->irq = platform_get_irq(pdev, 0);
> -	if (!keypad->irq) {
> -		err = -ENXIO;
> +	if (keypad->irq <= 0) {
> +		err = keypad->irq;

Argh, so what will happen if you return with keypad->irq == 0? Can you
please stop and consider what exactly  you are doing before churning
patches like crazy?

>  		goto failed_free;
>  	}
>  
> -- 
> 2.7.4
> 

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2017-11-18 18:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18 10:55 Arvind Yadav
2017-11-18 10:55 ` [PATCH 02/10 v3] Input: omap4-keypad: " Arvind Yadav
2017-11-18 10:55 ` [PATCH 03/10 v3] Input: twl4030_keypad: " Arvind Yadav
2017-11-18 10:55 ` [PATCH 04/10 v3] Input: serio: " Arvind Yadav
2017-11-18 10:55 ` [PATCH 05/10 v3] Input: cpcap-pwrbutton: Handle return value of platform_get_irq Arvind Yadav
2017-11-18 10:55 ` [PATCH 07/10 v3] Input: sun4i-ts: " Arvind Yadav
     [not found] ` <76d6a73ba51e1a8a86d8d9a1d0bbbf7723d5153a.1510999334.git.arvind.yadav.cs@gmail.com>
2017-11-18 10:55   ` [PATCH 06/10 v2] Input: w90p910_ts: " Arvind Yadav
2017-11-18 10:55   ` [PATCH 08/10 v3] Input: twl4030-pwrbutton: " Arvind Yadav
2017-11-18 10:55   ` [PATCH 09/10 v2] Input: sirfsoc-onkey: " Arvind Yadav
2017-11-18 10:55   ` [PATCH 10/10 v2] Input: palmas-pwrbutton: " Arvind Yadav
2017-11-18 18:30 ` Dmitry Torokhov [this message]
2017-11-20 16:24   ` [PATCH 01/10 v3] Input: ep93xx_keypad: Fix platform_get_irq's error checking arvindY

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=20171118183029.zooxomhrejzatuvd@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=maxime.ripard@free-electrons.com \
    --cc=mcuos.com@gmail.com \
    --cc=wens@csie.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

all inboxes | Powered by JetHome®