linux-kernel - Re: [PATCH v4 0/4] Do device node auto cleanup in drivers/soc/ti/

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: <172487049349.3438376.18165226507785538752.b4-ty@ti.com>
Date: Wed, 28 Aug 2024 13:41:57 -0500
From: Nishanth Menon <nm@...com>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        Santosh Shilimkar
	<ssantosh@...nel.org>,
        Nathan Chancellor <nathan@...nel.org>,
        Julia Lawall
	<julia.lawall@...ia.fr>,
        Kousik Sanagavarapu <five231003@...il.com>
CC: Nishanth Menon <nm@...com>, Shuah Khan <skhan@...uxfoundation.org>,
        Javier
 Carrasco <javier.carrasco.cruz@...il.com>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 0/4] Do device node auto cleanup in drivers/soc/ti/

Hi Kousik Sanagavarapu,

On Sun, 25 Aug 2024 14:18:41 +0530, Kousik Sanagavarapu wrote:
> Do "struct device_node" auto cleanup in soc/ti/.  This patch series takes
> care of all the cases where this is possible.
> 
> Thanks Nishanth for the review on the previous round.
> 
> v3:
> 
> [...]

I have applied the following to branch ti-drivers-soc-next on [1].
Thank you!

[1/4] soc: ti: pruss: factor out memories setup
      commit: 952ceb03787dde88fc713c7453824e25bf12cb3a
[2/4] soc: ti: pruss: do device_node auto cleanup
      commit: df70c0b4828bb85f1370453288a0a63d7618decf
[3/4] soc: ti: knav_qmss_queue: do device_node auto cleanup
      commit: b0289dbf1c952c04ba48b05cc6345381999ef055
[4/4] soc: ti: pm33xx: do device_node auto cleanup
      commit: 68123510b7c1c610387dd306f92ff539c3c546b5

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D