kernel-janitors.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: arvindY <arvind.yadav.cs@gmail.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	kernel-janitors@vger.kernel.org, Takashi Iwai <tiwai@suse.com>
Subject: Re: [alsa-devel] [PATCH 1/2] ASoC: nuc900: Fix platform_get_irq() error checking some more
Date: Sat, 09 Dec 2017 17:27:32 +0000	[thread overview]
Message-ID: <20171209172732.GF15660@piout.net> (raw)
In-Reply-To: <5A2BE644.3070009@gmail.com>

Arvind,

This was v5 and it contains an error that was corrected between v1 and
v2. For whatever reason, you reintroduced it between v4 and v5.

This is wasting a lot of time.

On 09/12/2017 at 19:03:56 +0530, arvindY wrote:
> Hi Dan,
> 
> On Saturday 09 December 2017 05:22 PM, Dan Carpenter wrote:
> > The error handling doesn't work here because "nuc900_audio->irq_num" is
> > unsigned.  Also we should be checking for < 0 and not <= 0 but I believe
> > that's harmless.  The platform_get_irq() comments don't talk about the
> > return values...
> Sorry for this  patch. I will fix it and send you updated patch.
> Thanks for point it.
> > Fixes: fa8cc38165c2 ("ASoC: nuc900: Fix platform_get_irq's error checking")
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > 
> > diff --git a/sound/soc/nuc900/nuc900-ac97.c b/sound/soc/nuc900/nuc900-ac97.c
> > index 5e4fbd2d3479..71fce7c85c93 100644
> > --- a/sound/soc/nuc900/nuc900-ac97.c
> > +++ b/sound/soc/nuc900/nuc900-ac97.c
> > @@ -345,11 +345,10 @@ static int nuc900_ac97_drvprobe(struct platform_device *pdev)
> >   		goto out;
> >   	}
> > -	nuc900_audio->irq_num = platform_get_irq(pdev, 0);
> > -	if (nuc900_audio->irq_num <= 0) {
> > -		ret = nuc900_audio->irq_num < 0 ? nuc900_audio->irq_num : -EBUSY;
> > +	ret = platform_get_irq(pdev, 0);
> > +	if (ret < 0)

The <= 0 was ok, see:
https://lkml.org/lkml/2017/11/18/41


-- 
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-12-09 17:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-09 11:52 [PATCH 1/2] ASoC: nuc900: Fix platform_get_irq() error checking some more Dan Carpenter
2017-12-09 11:52 ` [PATCH 2/2 resend] ASoC: nuc900: Fix a loop timeout test Dan Carpenter
2017-12-09 13:45 ` [PATCH 1/2] ASoC: nuc900: Fix platform_get_irq() error checking some more arvindY
2017-12-09 17:27   ` Alexandre Belloni [this message]
2017-12-09 18:49     ` [alsa-devel] " arvindY
2017-12-10  1:52     ` Dan Carpenter
2017-12-10  2:52       ` arvindY
2017-12-11  8:40         ` Dan Carpenter
2017-12-11  9:19           ` Arvind Yadav
2017-12-11 10:27             ` Dan Carpenter
2017-12-11 11:49               ` Alexandre Belloni
2017-12-11 12:01                 ` Dan Carpenter
2017-12-11 16:41                   ` Alexandre Belloni
2017-12-11 12:02                 ` Mark Brown
2017-12-11 12:14 ` Applied "ASoC: nuc900: Fix platform_get_irq() error checking some more" to the asoc tree Mark Brown

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=20171209172732.GF15660@piout.net \
    --to=alexandre.belloni@free-electrons.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arvind.yadav.cs@gmail.com \
    --cc=broonie@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.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).