linux-kernel - Re: [PATCH -next] ASoC: Intel: fix unused-variable warning in probe

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 14 Sep 2022 12:27:28 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Mark Brown <broonie@...nel.org>
Cc:     Gaosheng Cui <cuigaosheng1@...wei.com>, cezary.rojewski@...el.com,
        tiwai@...e.com, ranjani.sridharan@...ux.intel.com,
        pierre-louis.bossart@...ux.intel.com, perex@...ex.cz,
        liam.r.girdwood@...ux.intel.com, kai.vehmanen@...ux.intel.com,
        peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] ASoC: Intel: fix unused-variable warning in probe_codec

On Wed, 14 Sep 2022 11:40:17 +0200,
Mark Brown wrote:
> 
> On Mon, 22 Aug 2022 11:51:33 +0800, Gaosheng Cui wrote:
> > In configurations with CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC=n,
> > gcc warns about an unused variable:
> > 
> > sound/soc/intel/skylake/skl.c: In function ‘probe_codec’:
> > sound/soc/intel/skylake/skl.c:729:18: error: unused variable ‘skl’ [-Werror=unused-variable]
> >   struct skl_dev *skl = bus_to_skl(bus);
> >                   ^~~
> > cc1: all warnings being treated as errors
> > 
> > [...]
> 
> Applied to
> 
>    broonie/sound.git for-next
> 
> Thanks!
> 
> [1/1] ASoC: Intel: fix unused-variable warning in probe_codec
>       commit: 515626a33a194c4caaf2879dbf9e00e882582af0
> 
> 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.

I thought the buggy commit 3fd63658caed9 was present only in my tree
for now, but if it's in your tree, that's fine to apply through
yours.  Then I'll drop from mine.


thanks,

Takashi