linux-kernel - Re: [PATCH 0/2] ASoC: fsl_xcvr: Add suspend and resume 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: <173324825736.459040.7211694275678808457.b4-ty@kernel.org>
Date: Tue, 03 Dec 2024 17:50:57 +0000
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, 
 linuxppc-dev@...ts.ozlabs.org, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH 0/2] ASoC: fsl_xcvr: Add suspend and resume support

On Wed, 27 Nov 2024 11:00:33 +0800, Shengjiu Wang wrote:
> Define regmap for PHY and PLL registers, the PHY and PLL
> registers are accessed by AI interface in controller.
> Then  driver can use regcache to recover registers
> after suspend and resume.
> 
> Shengjiu Wang (2):
>   ASoC: fsl_xcvr: Use regmap for PHY and PLL registers
>   ASoC: fsl_xcvr: Add suspend and resume support
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: fsl_xcvr: Use regmap for PHY and PLL registers
      commit: 5a8b4785cddabfad348a96ca38eb0c3d735202df
[2/2] ASoC: fsl_xcvr: Add suspend and resume support
      commit: 297711ba0282abef38824b1e08c0ad6dcb6c4a53

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