mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
Cc: Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sound: pci: ice1712: wm8766.c:  Cleaning up uninitialized variables
Date: Sun, 01 Jun 2014 18:23:31 +0200	[thread overview]
Message-ID: <s5h38fovbss.wl%tiwai@suse.de> (raw)
In-Reply-To: <1401631371-21145-1-git-send-email-rickard_strandqvist@spectrumdigital.se>

At Sun,  1 Jun 2014 16:02:51 +0200,
Rickard Strandqvist wrote:
> 
> There is a risk that the variable will be used without being initialized.
> 
> This was largely found by using a static code analysis program called cppcheck.

It won't happen in reality.  And, initializing to some random values
isn't always received good.  You can use uninitialized_var() in such a
case, too.


Takashi

> 
> Signed-off-by: Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>
> ---
>  sound/pci/ice1712/wm8766.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/sound/pci/ice1712/wm8766.c b/sound/pci/ice1712/wm8766.c
> index 21b373b..788a31c 100644
> --- a/sound/pci/ice1712/wm8766.c
> +++ b/sound/pci/ice1712/wm8766.c
> @@ -237,7 +237,7 @@ static int snd_wm8766_ctl_get(struct snd_kcontrol *kcontrol,
>  {
>  	struct snd_wm8766 *wm = snd_kcontrol_chip(kcontrol);
>  	int n = kcontrol->private_value;
> -	u16 val1, val2;
> +	u16 val1 = 0, val2 = 0;
>  
>  	if (wm->ctl[n].get)
>  		wm->ctl[n].get(wm, &val1, &val2);
> -- 
> 1.7.10.4
> 

      reply	other threads:[~2014-06-01 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 14:02 Rickard Strandqvist
2014-06-01 16:23 ` Takashi Iwai [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=s5h38fovbss.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=rickard_strandqvist@spectrumdigital.se \
    /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®