linux-kernel - Re: [PATCH v2] ASoC: tas2781: Fix a warning reported by robot kernel test

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: <171504574426.1980570.10154577788713612869.b4-ty@kernel.org>
Date: Tue, 07 May 2024 10:35:44 +0900
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>
Cc: andriy.shevchenko@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz, 
 pierre-louis.bossart@...ux.intel.com, 13916275206@....com, 
 alsa-devel@...a-project.org, linux-kernel@...r.kernel.org, 
 liam.r.girdwood@...el.com, bard.liao@...el.com, 
 yung-chuan.liao@...ux.intel.com, kevin-lu@...com, 
 cameron.berkenpas@...il.com, tiwai@...e.de, baojun.xu@...com, soyer@....hu, 
 Baojun.Xu@....com
Subject: Re: [PATCH v2] ASoC: tas2781: Fix a warning reported by robot
 kernel test

On Sun, 05 May 2024 20:23:45 +0800, Shenghao Ding wrote:
> Fix a warning reported by robot kernel test that 'fw_entry' in function
> 'tas2781_load_calibration' is used uninitialized with compiler
> sh4-linux-gcc (GCC) 13.2.0, an update of copyright and a correction of the
> comments.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: tas2781: Fix a warning reported by robot kernel test
      commit: 1ae14f3520b1a0ad144610a3f592c81a3e81cd1b

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