linux-kernel - Re: [PATCH v2 0/2] ASoC: stm32: i2s: add stm32mp25 support

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: <173112203540.168194.9961366675088520447.b4-ty@kernel.org>
Date: Sat, 09 Nov 2024 03:13:55 +0000
From: Mark Brown <broonie@...nel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Maxime Coquelin <mcoquelin.stm32@...il.com>, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 Olivier Moysan <olivier.moysan@...s.st.com>
Cc: linux-sound@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ASoC: stm32: i2s: add stm32mp25 support

On Thu, 07 Nov 2024 15:47:10 +0100, Olivier Moysan wrote:
> Update STM32 I2S driver and binding to support STM32MP25 SoCs.
> 
> Changes in v2:
> - Rearrange clocks and clock-names ranges depending on compatible.
> 
> Olivier Moysan (2):
>   ASoC: dt-bindings: add stm32mp25 support for i2s
>   ASoC: stm32: i2s: add stm32mp25 support
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: add stm32mp25 support for i2s
      commit: c69b7edc10d2fff4bcb3dd464ee26cbf22818fec
[2/2] ASoC: stm32: i2s: add stm32mp25 support
      commit: 125d0f698ad500b0092812e52a6c342ba055ae68

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