linux-kernel - Re: [PATCH] spi: omap2-mcspi: Fix the IS_ERR() bug for devm_clk_get_optional

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: <173340609921.87421.2165857099937592834.b4-ty@kernel.org>
Date: Thu, 05 Dec 2024 13:41:39 +0000
From: Mark Brown <broonie@...nel.org>
To: psiddaiah@...sta.com
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 cminyard@...sta.com
Subject: Re: [PATCH] spi: omap2-mcspi: Fix the IS_ERR() bug for
 devm_clk_get_optional_enabled()

On Thu, 05 Dec 2024 12:34:26 +0530, psiddaiah@...sta.com wrote:
> The devm_clk_get_optional_enabled() function returns error
> pointers(PTR_ERR()). So use IS_ERR() to check it.
> 
> Verified on K3-J7200 EVM board, without clock node mentioned
> in the device tree.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: omap2-mcspi: Fix the IS_ERR() bug for devm_clk_get_optional_enabled()
      commit: 4c6ac5446d060f0bf435ccc8bc3aa7b7b5f718ad

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