From: Kousik Sanagavarapu <five231003@gmail.com>
To: Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Julia Lawall <julia.lawall@inria.fr>
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 0/3] Use scope based cleanup in drivers/soc/ti/
Date: Fri, 10 May 2024 12:43:21 +0530 [thread overview]
Message-ID: <20240510071432.62913-1-five231003@gmail.com> (raw)
Do scope based "struct device_node" cleanup in drivers/soc/ti/*. This
covers all the possible cases.
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 | 17 ++++++-----
drivers/soc/ti/pm33xx.c | 20 +++++--------
drivers/soc/ti/pruss.c | 48 +++++++++++---------------------
3 files changed, 31 insertions(+), 54 deletions(-)
--
2.45.0.rc1.8.ge326e52010
next reply other threads:[~2024-05-10 7:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 7:13 Kousik Sanagavarapu [this message]
2024-05-10 7:13 ` [PATCH 1/3] soc: ti: pruss: do device_node auto cleanup Kousik Sanagavarapu
2024-05-16 14:41 ` Jonathan Cameron
2024-05-10 7:13 ` [PATCH 2/3] soc: ti: knav_qmss_queue: " Kousik Sanagavarapu
2024-05-11 10:12 ` kernel test robot
2024-05-12 10:26 ` Kousik Sanagavarapu
2024-05-12 10:36 ` Julia Lawall
2024-05-13 6:44 ` Nathan Chancellor
2024-05-13 7:23 ` Kousik Sanagavarapu
2024-05-16 14:48 ` Jonathan Cameron
2024-05-10 7:13 ` [PATCH 3/3] soc: ti: pm33xx: " Kousik Sanagavarapu
2024-05-11 9:06 ` [PATCH 0/3] Use scope based cleanup in drivers/soc/ti/ 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=20240510071432.62913-1-five231003@gmail.com \
--to=five231003@gmail.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).