linux-kernel - Re: [PATCH] ASoC: rt5682: Return devm_of_clk_add_hw

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: <172540382935.163502.3517411145931559366.b4-ty@kernel.org>
Date: Tue, 03 Sep 2024 23:50:29 +0100
From: Mark Brown <broonie@...nel.org>
To: oder_chiou@...ltek.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, derek.fang@...ltek.com, Ma Ke <make24@...as.ac.cn>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 stable@...r.kernel.org
Subject: Re: [PATCH] ASoC: rt5682: Return devm_of_clk_add_hw_provider to
 transfer the error

On Fri, 30 Aug 2024 22:31:54 +0800, Ma Ke wrote:
> Return devm_of_clk_add_hw_provider() in order to transfer the error, if it
> fails due to resource allocation failure or device tree clock provider
> registration failure.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: rt5682: Return devm_of_clk_add_hw_provider to transfer the error
      commit: fcca6d05ef49d5650514ea1dcfd12e4ae3ff2be6

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