linux-kernel - Re: [PATCH v6 0/7] TAS2562 issue fixes and slot programming

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]

Date:   Thu, 25 Jun 2020 20:11:57 +0100
From:   Mark Brown <broonie@...nel.org>
To:     tiwai@...e.com, perex@...ex.cz, Dan Murphy <dmurphy@...com>,
        lgirdwood@...il.com
Cc:     robh@...nel.org, devicetree@...r.kernel.org,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 0/7] TAS2562 issue fixes and slot programming

On Wed, 24 Jun 2020 12:49:25 -0500, Dan Murphy wrote:
> This series fixes issues tih the shut-down gpio device tree allocation and a
> code format issue found.
> 
> While working on a project slot programming for the tx and rx paths needed to be
> enabled.  In addition the vsense slot programming needed to be configurable and
> not directly a simpler adder to the isense slot.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: tas2562: Fix shut-down gpio property
      commit: 6f81e520b2906258a063f09b8d1dd9d0cc6a3172
[2/6] ASoC: tas2562: Update shutdown GPIO property
      commit: bc07b54459cbb3a572a78b5c200ff79ef11b8158
[3/6] ASoC: tas2562: Fix format issue for extra space before a comma
      commit: c8294da2ed0be726bb87019eba3a6367c7f1c922
[4/6] ASoC: tas2562: Add rx and tx slot programming
      (no commit info)
[5/6] dt-bindings: tas2562: Add voltage sense slot property
      (no commit info)
[6/6] ASoC: tas2562: Add voltage sense slot configuration
      (no commit info)

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