linux-kernel - Re: [PATCH] ASoC: tas2562: Remove duplicate code for I/V sense

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: <160078710095.52882.10146545480873734232.b4-ty@kernel.org>
Date:   Tue, 22 Sep 2020 16:05:06 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, tiwai@...e.com, robh+dt@...nel.org,
        Dan Murphy <dmurphy@...com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH] ASoC: tas2562: Remove duplicate code for I/V sense

On Tue, 22 Sep 2020 09:24:11 -0500, Dan Murphy wrote:
> Remove duplicate code for programming the I/V sense the call to update
> the register was duplicated in commit 09ed395b05feb ("ASoC: tas2562:
> Add voltage sense slot configuration").

Applied to

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

Thanks!

[1/1] ASoC: tas2562: Remove duplicate code for I/V sense
      commit: 90e2a588c9e743f104849fb2da4c121e1a487201

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