linux-kernel - Re: [PATCH] ASoC: qcom: Fix typo error in HDMI regmap config callbacks

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <161228008450.11888.13128911236969601728.b4-ty@kernel.org>
Date:   Tue, 02 Feb 2021 15:34:44 +0000
From:   Mark Brown <broonie@...nel.org>
To:     devicetree@...r.kernel.org, perex@...ex.cz,
        alsa-devel@...a-project.org, agross@...nel.org,
        Srinivasa Rao Mandadapu <srivasam@...eaurora.org>,
        robh+dt@...nel.org, rohitkr@...eaurora.org,
        linux-arm-msm@...r.kernel.org, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, bjorn.andersson@...aro.org,
        bgoswami@...eaurora.org, swboyd@...omium.org, plai@...eaurora.org,
        srinivas.kandagatla@...aro.org, tiwai@...e.com
Subject: Re: [PATCH] ASoC: qcom: Fix typo error in HDMI regmap config callbacks

On Tue, 2 Feb 2021 11:57:27 +0530, Srinivasa Rao Mandadapu wrote:
> Had a typo in lpass platform driver that resulted in crash
> during suspend/resume with an HDMI dongle connected.
> 
> The regmap read/write/volatile regesters validation callbacks in lpass-cpu
> were using MI2S rdma_channels count instead of hdmi_rdma_channels.
> 
> This typo error causing to read registers from the regmap beyond the length
> of the mapping created by ioremap().
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: Fix typo error in HDMI regmap config callbacks
      commit: 6c9123068815ed0bc1e8fa5a5029eef5ee3866c3

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