From: Kousik Sanagavarapu <five231003@gmail.com>
To: Julia Lawall <julia.lawall@inria.fr>, Nishanth Menon <nm@ti.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kousik Sanagavarapu <five231003@gmail.com>
Subject: [PATCH v2 0/3] Do device node auto cleanup in drivers/soc/ti/
Date: Wed, 3 Jul 2024 12:25:25 +0530 [thread overview]
Message-ID: <20240703065710.13786-1-five231003@gmail.com> (raw)
Do "struct device_node" auto cleanup in soc/ti/. This patch series takes
care of all the cases where this is possible.
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.
Sorry for sending the v2 so late. I was busy with my semester exams.
Kousik Sanagavarapu (3):
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 | 85 +++++++++-------
drivers/soc/ti/pm33xx.c | 20 ++--
drivers/soc/ti/pruss.c | 168 ++++++++++++++-----------------
3 files changed, 131 insertions(+), 142 deletions(-)
--
2.45.2.561.g66ac6e4bcd
next reply other threads:[~2024-07-03 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 6:55 Kousik Sanagavarapu [this message]
2024-07-03 6:55 ` [PATCH v2 1/3] soc: ti: pruss: do device_node auto cleanup Kousik Sanagavarapu
2024-07-05 10:49 ` Jonathan Cameron
2024-07-03 6:55 ` [PATCH v2 2/3] soc: ti: knav_qmss_queue: " Kousik Sanagavarapu
2024-07-05 10:52 ` Jonathan Cameron
2024-07-03 6:55 ` [PATCH v2 3/3] soc: ti: pm33xx: " Kousik Sanagavarapu
2024-07-05 10:54 ` Jonathan Cameron
2024-07-05 11:11 ` Kousik Sanagavarapu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240703065710.13786-1-five231003@gmail.com \
--to=five231003@gmail.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=julia.lawall@inria.fr \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nm@ti.com \
--cc=skhan@linuxfoundation.org \
--cc=ssantosh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.