linux-kernel - Re: [PATCH v2] ASoC: intel/sdw_utils: Assign initial value in asoc_sdw_rt_amp_spk_rtd

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: <174729451152.272498.2680302769777134595.b4-ty@kernel.org>
Date: Thu, 15 May 2025 09:35:11 +0200
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, I Hsin Cheng <richard120310@...il.com>
Cc: perex@...ex.cz, tiwai@...e.com, pierre-louis.bossart@...ux.dev, 
 yung-chuan.liao@...ux.intel.com, Vijendar.Mukunda@....com, 
 peter.ujfalusi@...ux.intel.com, christophe.jaillet@...adoo.fr, 
 peterz@...radead.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, skhan@...uxfoundation.org
Subject: Re: [PATCH v2] ASoC: intel/sdw_utils: Assign initial value in
 asoc_sdw_rt_amp_spk_rtd_init()

On Tue, 06 May 2025 02:54:23 +0800, I Hsin Cheng wrote:
> Initialize "ret" with "-EINVAL" to handle cases where "strstr()" for
> "codec_dai->component->name_prefix" doesn't find "-1" nor "-2". In that
> case "name_prefix" is invalid because for current implementation it's
> expected to have either "-1" or "-2" in it. (Maybe "-3", "-4" and so on
> in the future.)
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: intel/sdw_utils: Assign initial value in asoc_sdw_rt_amp_spk_rtd_init()
      commit: 5fb3878216aece471af030b33a9fbef3babd8617

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