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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173741127845.104623.1779188125305683967.b4-ty@kernel.org>
Date: Mon, 20 Jan 2025 22:14:38 +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, 
 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: two fixes for asrc memory to memory

On Mon, 20 Jan 2025 16:19:36 +0800, Shengjiu Wang wrote:
> 1. Fix the suspend failure for memory to peripheral function.
> 2. Return error value for processing function.
> 
> Shengjiu Wang (2):
>   ASoC: fsl_asrc_m2m: only handle pairs for m2m in the suspend
>   ASoC: fsl_asrc_m2m: return error value in asrc_m2m_device_run()
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: fsl_asrc_m2m: only handle pairs for m2m in the suspend
      commit: d12ca6d4c31bf974ecc80e36761488f41d05d18b
[2/2] ASoC: fsl_asrc_m2m: return error value in asrc_m2m_device_run()
      commit: abe01a78bfc8be9cc025a73b991c4e77431de9de

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ