linux-kernel - Re: [PATCH 1/2] ASoC: tlv320adcx140: Fix GPO register start address

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: <159614804535.1473.15036781071494882878.b4-ty@kernel.org>
Date:   Thu, 30 Jul 2020 23:27:39 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com,
        Dan Murphy <dmurphy@...com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] ASoC: tlv320adcx140: Fix GPO register start address

On Thu, 30 Jul 2020 09:24:18 -0500, Dan Murphy wrote:
> The header was updated to align with the data sheet to start the GPO_CFG
> at GPO_CFG0.  The code was not updated to the change and therefore the
> GPO_CFG0 register was not written to.

Applied to

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

Thanks!

[1/2] ASoC: tlv320adcx140: Fix GPO register start address
      commit: 806a8afedef82c5f156b1c9b1de1205f9abfd21e
[2/2] ASoC: tlv320adcx140: Move device reset to before programming
      commit: 982f4a4134893cd48c466e7a56422d7c65837d10

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