linux-kernel - Re: [PATCH] spi: spi-s3c64xx.c: Remove of_node

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]

Date: Wed, 24 Apr 2024 22:58:12 +0900
From: Mark Brown <broonie@...nel.org>
To: andi.shyti@...nel.org, krzysztof.kozlowski@...aro.org, 
 alim.akhtar@...sung.com, Shivani Gupta <shivani07g@...il.com>
Cc: linux-spi@...r.kernel.org, linux-samsung-soc@...r.kernel.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, 
 skhan@...uxfoundation.org, javier.carrasco.cruz@...il.com, 
 Julia Lawall <julia.lawall@...ia.fr>
Subject: Re: [PATCH] spi: spi-s3c64xx.c: Remove of_node_put for auto
 cleanup

On Thu, 18 Apr 2024 00:05:05 +0000, Shivani Gupta wrote:
> Use the scope based of_node_put() cleanup in s3c64xx_spi_csinfo to
> automatically release the device node with the __free() cleanup handler
> Initialize data_np at the point of declaration for clarity of scope.
> 
> This change reduces the risk of memory leaks and simplifies the code by
> removing manual node put call.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-s3c64xx.c: Remove of_node_put for auto cleanup
      commit: abba116f601800a0c74b9a9c2c91e2eebca791c1

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