linux-kernel - Re: [PATCH] ASoC: component: suppress uninitialized-variable warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <158817756637.27768.10087269743867746681.b4-ty@kernel.org>
Date:   Wed, 29 Apr 2020 17:26:06 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Arnd Bergmann <arnd@...db.de>
Cc:     Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Takashi Iwai <tiwai@...e.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        Liam Girdwood <lgirdwood@...il.com>,
        Shreyas NC <shreyas.nc@...el.com>
Subject: Re: [PATCH] ASoC: component: suppress uninitialized-variable warning

On Tue, 28 Apr 2020 23:47:31 +0200, Arnd Bergmann wrote:
> Old versions of gcc (tested on gcc-4.8) produce a warning for
> correct code:
> 
> sound/soc/soc-compress.c: In function 'soc_compr_open':
> sound/soc/soc-compress.c:75:28: error: 'component' is used uninitialized in this function [-Werror=uninitialized]
>   struct snd_soc_component *component, *save = NULL;
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.8

Thanks!

[1/1] ASoC: component: suppress uninitialized-variable warning
      commit: be16a0f0dc8fab8e25d9cdbeb4f8f28afc9186d2

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark