linux-kernel - Re: [RESEND] Asoc: qcom: lpass-cpu: Mark HDMI TX parity register as volatile

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: <166619961841.1416660.6646939908532904224.b4-ty@kernel.org>
Date:   Wed, 19 Oct 2022 18:13:38 +0100
From:   Mark Brown <broonie@...nel.org>
To:     devicetree@...r.kernel.org, swboyd@...omium.org,
        linux-kernel@...r.kernel.org, quic_rohkumar@...cinc.com,
        linux-arm-msm@...r.kernel.org, bgoswami@...cinc.com,
        judyhsiao@...omium.org, alsa-devel@...a-project.org,
        andersson@...nel.org, srinivas.kandagatla@...aro.org,
        lgirdwood@...il.com, quic_plai@...cinc.com, agross@...nel.org,
        tiwai@...e.com, robh+dt@...nel.org,
        Srinivasa Rao Mandadapu <quic_srivasam@...cinc.com>,
        perex@...ex.cz
Subject: Re: [RESEND] Asoc: qcom: lpass-cpu: Mark HDMI TX parity register as volatile

On Sat, 15 Oct 2022 14:48:50 +0530, Srinivasa Rao Mandadapu wrote:
> Update LPASS_HDMI_TX_PARITY_ADDR register as volatile, to fix
> dp audio failures observed with some of external monitors.
> 
> Fixes: 7cb37b7bd0d3 ("ASoC: qcom: Add support for lpass hdmi driver")
> 
> 

Applied to

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

Thanks!

[1/1] Asoc: qcom: lpass-cpu: Mark HDMI TX parity register as volatile
      commit: 1dd5166102e7ca91e8c5d833110333835e147ddb

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