mbox series

[v4,0/4] Do device node auto cleanup in drivers/soc/ti/

Message ID 20240825085714.10736-1-five231003@gmail.com (mailing list archive)
Headers show
Series Do device node auto cleanup in drivers/soc/ti/ | expand

Message

Kousik Sanagavarapu Aug. 25, 2024, 8:48 a.m. UTC 
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:

	https://lore.kernel.org/linux-arm-kernel/20240707055341.3656-1-five231003@gmail.com/

Changes since v3:
- s/seperate/separate in the commit msgs througout.
- 1 / 4 - "return ret" instead of "goto rpm_put" as pm_runtime was never
  enabled by the time we call pruss_of_setup_memories() in case we
  return on err.

v2:

	https://lore.kernel.org/linux-arm-kernel/20240703065710.13786-1-five231003@gmail.com/

Changes since v2:
- Split v2 1/3 into v3 1/4 and v3 2/4.  The memory setup code is
  seperated out of the pruss_probe() function and put into 1/4 and the
  actual conversion to auto cleanup is done in 2/4.
- Replace dev_err() with dev_err_probe() in the code paths touched.

v1:

	https://lore.kernel.org/linux-arm-kernel/20240510071432.62913-1-five231003@gmail.com/

Changes since v1:
- Refactor code so that it the scope of the pointers touched is reduced,
  making the code look more clean.
- The above also the side-effect of fixing the errors that clang emitted
  (but my local version of gcc didn't) for PATCH 2/3 during v1.
Kousik Sanagavarapu (4):
  soc: ti: pruss: factor out memories setup
  soc: ti: pruss: do device_node auto cleanup
  soc: ti: knav_qmss_queue: do device_node auto cleanup
  soc: ti: pm33xx: do device_node auto cleanup

 drivers/soc/ti/knav_qmss_queue.c | 100 +++++++++---------
 drivers/soc/ti/pm33xx.c          |  52 ++++-----
 drivers/soc/ti/pruss.c           | 176 ++++++++++++++-----------------
 3 files changed, 155 insertions(+), 173 deletions(-)

Comments

Nishanth Menon Aug. 28, 2024, 6:41 p.m. UTC | #1 
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