linux-kernel - Re: [PATCH] ASoC: codecs: es8326: Fix DTS properties reading

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: <167571945073.1296981.607333949793064897.b4-ty@kernel.org>
Date:   Mon, 06 Feb 2023 21:37:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Alexey Firago <a.firago@...ro.com>
Cc:     alsa-devel@...a-project.org, zhuning0077@...il.com,
        yangyingliang@...wei.com, yangxiaohua@...rest-semi.com,
        tiwai@...e.com
Subject: Re: [PATCH] ASoC: codecs: es8326: Fix DTS properties reading

On Sat, 04 Feb 2023 22:51:06 +0300, Alexey Firago wrote:
> Seems like properties parsing and reading was copy-pasted,
> so "everest,interrupt-src" and "everest,interrupt-clk" are saved into
> the es8326->jack_pol variable. This might lead to wrong settings
> being saved into the reg 57 (ES8326_HP_DET).
> 
> Fix this by using proper variables while reading properties.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: codecs: es8326: Fix DTS properties reading
      commit: fe1e7e8ce2c47bd8fd9885eab63fca0a522e94c9

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