linux-kernel - Re: [PATCH v2 0/2] ASoC: fsl_xcvr: Support i.MX95 platform

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]

Date: Wed, 05 Jun 2024 22:38:11 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, robh+dt@...nel.org, 
 krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org, 
 shengjiu.wang@...il.com, linux-sound@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Xiubo.Lee@...il.com, festevam@...il.com, nicoleotsuka@...il.com, 
 perex@...ex.cz, tiwai@...e.com, alsa-devel@...a-project.org, 
 linuxppc-dev@...ts.ozlabs.org, Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH v2 0/2] ASoC: fsl_xcvr: Support i.MX95 platform

On Tue, 14 May 2024 11:12:07 +0800, Shengjiu Wang wrote:
> On i.MX95 wakeup domain, there is one instance of Audio XCVR
> supporting SPDIF mode with a connection to the Audio XCVR physical
> interface.
> 
> changes in v2:
> - Merge patch 1&2, 3&4 from v1 together.
> - Add more comments in commit message
> - Add constaint for clocks used on i.mx95
> - Add 'select SND_SOC_FSL_UTILS' for compiling issue.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: fsl,xcvr: Add compatible string for i.MX95
      commit: fc1277335ffa0d180c76ddccf5fe27fc75674e67
[2/2] ASoC: fsl_xcvr: Add support for i.MX95 platform
      commit: f13b349e3c70320ef5a86edfc888a6feb612abb0

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