linux-kernel - Re: [PATCH 0/2] Updates for mchp-spdif(tx/rx)

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: <172780518782.2298697.5345133650915671833.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 18:53:07 +0100
From: Mark Brown <broonie@...nel.org>
To: claudiu.beznea@...on.dev, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, nicolas.ferre@...rochip.com, alexandre.belloni@...tlin.com, 
 Andrei Simion <andrei.simion@...rochip.com>
Cc: alsa-devel@...a-project.org, linux-sound@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Updates for mchp-spdif(tx/rx)

On Mon, 16 Sep 2024 12:10:55 +0300, Andrei Simion wrote:
> This patch set includes two updates for the MCHP SPDIF RX and TX drivers.
> The patches remove the interface name from the stream_name, allowing the
> interface name and index to be set in the Device Tree (DT) using the
> sound-name-prefix string property.
> 
> Codrin Ciubotariu (2):
>   ASoC: atmel: mchp-spdiftx: Remove interface name from stream_name
>   ASoC: atmel: mchp-spdifrx: Remove interface name from stream_name
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: atmel: mchp-spdiftx: Remove interface name from stream_name
      commit: a6ae5845f0231fb1b3e9bf591b237d99d1a077c0
[2/2] ASoC: atmel: mchp-spdifrx: Remove interface name from stream_name
      commit: 3c44a715e389929b8243d6a0545992d78cff6cba

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