linux-kernel - Re: [PATCH next] ASoc: tas2783A: Fix an error code 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] [day] [month] [year] [list]

Message-Id: <175890753427.2509416.7801317102009548908.b4-ty@kernel.org>
Date: Fri, 26 Sep 2025 18:25:34 +0100
From: Mark Brown <broonie@...nel.org>
To: Niranjan H Y <niranjan.hy@...com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Shenghao Ding <shenghao-ding@...com>, Kevin Lu <kevin-lu@...com>, 
 Baojun Xu <baojun.xu@...com>, Liam Girdwood <lgirdwood@...il.com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Bard Liao <yung-chuan.liao@...ux.intel.com>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] ASoc: tas2783A: Fix an error code in probe()

On Fri, 26 Sep 2025 07:03:11 +0300, Dan Carpenter wrote:
> This code returns the wrong variable "tas_dev->regmap" instead of
> "regmap" so it returns success instead of a negative error code.
> Return the correct variable.
> 
> 

Applied to

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

Thanks!

[1/1] ASoc: tas2783A: Fix an error code in probe()
      commit: f8b9c819ea20d1101656a91ced843d9e47ba0630

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