linux-kernel - Re: [PATCH 0/2] Add support for the TAS5733

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: <167810950662.75807.17494624901046895740.b4-ty@kernel.org>
Date:   Mon, 06 Mar 2023 13:31:46 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Kevin Cernekee <cernekee@...omium.org>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Hans Verkuil <hverkuil-cisco@...all.nl>,
        Crt Mori <cmo@...exis.com>, alsa-devel@...a-project.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        Kamel Bouhara <kamel.bouhara@...tlin.com>
Subject: Re: [PATCH 0/2] Add support for the TAS5733

On Wed, 22 Feb 2023 09:32:58 +0100, Kamel Bouhara wrote:
> This small series extends the tas571x driver to support the TAS5733
> audio power amplifier.
> 
> Kamel Bouhara (2):
>   ASoC: tas571x: add tas5733 compatible
>   ASoC: tas571x: add support for TAS5733
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: tas571x: add tas5733 compatible
      commit: 95a29d5f626a37dbefd0883f294ec4e22a8a7911
[2/2] ASoC: tas571x: add support for TAS5733
      commit: f5db4d00f73871988beba0277ea29cff73d38445

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