linux-kernel - Re: [PATCH v3 0/2] ASoC: add support for TAS5805M digital amplifier

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: <164310602619.74844.8879999031786613742.b4-ty@kernel.org>
Date:   Tue, 25 Jan 2022 10:20:26 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Daniel Beer <daniel.beer@...rinstitute.com>,
        devicetree@...r.kernel.org
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Derek Simkowiak <derek.simkowiak@...rinstitute.com>,
        Andy Liu <andy-liu@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] ASoC: add support for TAS5805M digital amplifier

On Sun, 16 Jan 2022 14:58:56 +1300, Daniel Beer wrote:
> This pair of patches implements support for the TAS5805M class D audio
> amplifier. This driver, and the example configuration in the device-tree
> file, were originally based on a 4.19 series kernel and have been
> modified slightly from the tested version.
> 
> This resubmission differs from v2 as follows:
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: add support for TAS5805M digital amplifier
      commit: 2e5a74c68d601b11a496f91f76fa7bb236d10bd0
[2/2] ASoC: dt-bindings: add bindings for TI TAS5805M.
      commit: b8aec7a4a01b75973c22f004377a48593a3fef03

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