From: Mark Brown <broonie@sirena.org.uk>
To: Julien Brunel <brunel@diku.dk>
Cc: tiwai@suse.de, Geoffrey Wossum <geoffrey@pager.net>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] sound/soc/at32: Useless NULL test
Date: Fri, 26 Sep 2008 15:00:23 +0100 [thread overview]
Message-ID: <20080926140021.GD15493@sirena.org.uk> (raw)
In-Reply-To: <200809261523.46747.brunel@diku.dk>
On Fri, Sep 26, 2008 at 03:23:46PM +0200, Julien Brunel wrote:
> The test (ssc != NULL) can only be reached if the call to the function
> ssc_request, the result of which ssc is assigned, succeeds. Moreover,
> statements assign NULL to ssc just before a return, which is useless
> since it is a local variable. So, we suggest to delete the test and
> the two assignments.
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
For future reference if you're submitting other similar things (which I
guess you will given that you've got a tool to check for this stuff)
it'd be helpful if you could rewrite the explanation for the NULL test
to be something like:
The test (ssc != NULL) is redundant since it can only be reached
when ssc is guaranteed to have been set to a valid ssc.
which is much easier to parse.
> diff -u -p a/sound/soc/at32/playpaq_wm8510.c b/sound/soc/at32/playpaq_wm8510.c
> --- a/sound/soc/at32/playpaq_wm8510.c
> +++ b/sound/soc/at32/playpaq_wm8510.c
> @@ -405,7 +405,6 @@ static int __init playpaq_asoc_init(void
> ssc = ssc_request(0);
> if (IS_ERR(ssc)) {
> ret = PTR_ERR(ssc);
> - ssc = NULL;
> goto err_ssc;
> }
> ssc_p->ssc = ssc;
> @@ -476,10 +475,7 @@ err_pll0:
> _gclk0 = NULL;
> }
> err_gclk0:
> - if (ssc != NULL) {
> - ssc_free(ssc);
> - ssc = NULL;
> - }
> + ssc_free(ssc);
next prev parent reply other threads:[~2008-09-26 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 13:23 Julien Brunel
2008-09-26 14:00 ` Mark Brown [this message]
2008-09-26 14:45 ` Takashi Iwai
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=20080926140021.GD15493@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=brunel@diku.dk \
--cc=geoffrey@pager.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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 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®