linux-kernel - Re: [PATCH v2 0/2] Updates for Atmel SSC DAI

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: <172780519017.2298697.15357043212367234961.b4-ty@kernel.org>
Date: Tue, 01 Oct 2024 18:53:10 +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 v2 0/2] Updates for Atmel SSC DAI

On Mon, 16 Sep 2024 16:19:08 +0300, Andrei Simion wrote:
> This patch set includes two updates for the Atmel SSC DAI driver:
> - Address the limitation with the S24_LE format.
> - Add stream names for DPCM and future use-cases.
> 
> Codrin Ciubotariu (2):
>   ASoC: atmel: atmel_ssc_dai: Add stream names
>   ASoC: atmel: atmel_ssc_dai: Drop S24_LE support due to single channel
>     limitation
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: atmel: atmel_ssc_dai: Add stream names
      commit: 879c9151572317e8ddb6ab6c57a7689bf580efc9
[2/2] ASoC: atmel: atmel_ssc_dai: Drop S24_LE support due to single channel limitation
      commit: ac8775d7de5a8ccac225a398cbce9fb9fffdbb9f

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