From: Takashi Iwai <tiwai@suse.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ALSA: mixart: silence unitialized variable warnings
Date: Tue, 15 Mar 2016 10:01:35 +0100 [thread overview]
Message-ID: <s5hio0ogln4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160315070917.GE13560@mwanda>
On Tue, 15 Mar 2016 08:09:17 +0100,
Dan Carpenter wrote:
>
> We print can print the uninitialized memory on error. Which is an info
> leak, I suppose but it's basically harmless.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks.
Takashi
>
> diff --git a/sound/pci/mixart/mixart_mixer.c b/sound/pci/mixart/mixart_mixer.c
> index 24a1955..58fd79eb 100644
> --- a/sound/pci/mixart/mixart_mixer.c
> +++ b/sound/pci/mixart/mixart_mixer.c
> @@ -726,7 +726,7 @@ int mixart_update_playback_stream_level(struct snd_mixart* chip, int is_aes, int
> int volume[2];
> struct mixart_msg request;
> struct mixart_set_out_stream_level_req set_level;
> - u32 status;
> + u32 status = 0;
> struct mixart_pipe *pipe;
>
> memset(&set_level, 0, sizeof(set_level));
> @@ -778,7 +778,7 @@ int mixart_update_capture_stream_level(struct snd_mixart* chip, int is_aes)
> struct mixart_pipe *pipe;
> struct mixart_msg request;
> struct mixart_set_in_audio_level_req set_level;
> - u32 status;
> + u32 status = 0;
>
> if(is_aes) {
> idx = 1;
>
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ALSA: mixart: silence unitialized variable warnings
Date: Tue, 15 Mar 2016 09:01:35 +0000 [thread overview]
Message-ID: <s5hio0ogln4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160315070917.GE13560@mwanda>
On Tue, 15 Mar 2016 08:09:17 +0100,
Dan Carpenter wrote:
>
> We print can print the uninitialized memory on error. Which is an info
> leak, I suppose but it's basically harmless.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks.
Takashi
>
> diff --git a/sound/pci/mixart/mixart_mixer.c b/sound/pci/mixart/mixart_mixer.c
> index 24a1955..58fd79eb 100644
> --- a/sound/pci/mixart/mixart_mixer.c
> +++ b/sound/pci/mixart/mixart_mixer.c
> @@ -726,7 +726,7 @@ int mixart_update_playback_stream_level(struct snd_mixart* chip, int is_aes, int
> int volume[2];
> struct mixart_msg request;
> struct mixart_set_out_stream_level_req set_level;
> - u32 status;
> + u32 status = 0;
> struct mixart_pipe *pipe;
>
> memset(&set_level, 0, sizeof(set_level));
> @@ -778,7 +778,7 @@ int mixart_update_capture_stream_level(struct snd_mixart* chip, int is_aes)
> struct mixart_pipe *pipe;
> struct mixart_msg request;
> struct mixart_set_in_audio_level_req set_level;
> - u32 status;
> + u32 status = 0;
>
> if(is_aes) {
> idx = 1;
>
next prev parent reply other threads:[~2016-03-15 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 7:09 [patch] ALSA: mixart: silence unitialized variable warnings Dan Carpenter
2016-03-15 7:09 ` Dan Carpenter
2016-03-15 9:01 ` Takashi Iwai [this message]
2016-03-15 9:01 ` 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=s5hio0ogln4.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=perex@perex.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.