linux-kernel - Re: [PATCH 0/2] ASoC: fsl_xcvr: get channel status data in two cases

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: <175339870611.186504.5168876077229345217.b4-ty@kernel.org>
Date: Fri, 25 Jul 2025 00:11:46 +0100
From: Mark Brown <broonie@...nel.org>
To: shengjiu.wang@...il.com, Xiubo.Lee@...il.com, festevam@...il.com, 
 nicoleotsuka@...il.com, lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 linux-sound@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, 
 linux-kernel@...r.kernel.org, Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH 0/2] ASoC: fsl_xcvr: get channel status data in two
 cases

On Thu, 10 Jul 2025 11:04:03 +0800, Shengjiu Wang wrote:
> There is two different cases for getting channel status data:
> 1. With PHY exists, there is firmware running on M core, the firmware
> should fill the channel status to RAM space, driver need to read them
> from RAM.
> 2. Without PHY, the channel status need to be obtained from registers.
> 
> Shengjiu Wang (2):
>   ASoC: fsl_xcvr: get channel status data when PHY is not exists
>   ASoC: fsl_xcvr: get channel status data with firmware exists
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: fsl_xcvr: get channel status data when PHY is not exists
      commit: ca592e20659e0304ebd8f4dabb273da4f9385848
[2/2] ASoC: fsl_xcvr: get channel status data with firmware exists
      commit: 6776ecc9dd587c08a6bb334542f9f8821a091013

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