From: Jisheng Zhang <jszhang@kernel.org>
To: "Rafael J . Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@kernel.org>, Len Brown <lenb@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>
Cc: linux-pm@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH] PM: Use LIST_HEAD() to initialize on stack list head
Date: Tue, 19 May 2026 13:59:20 +0800 [thread overview]
Message-ID: <20260519055920.13180-1-jszhang@kernel.org> (raw)
Use LIST_HEAD to initialize on stack list head. No intentional
functional impact.
Change generated with below coccinelle script:
@@
identifier name;
@@
- struct list_head name;
+ LIST_HEAD(name);
... when != name
- INIT_LIST_HEAD(&name);
Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
---
drivers/base/power/clock_ops.c | 4 +---
drivers/base/power/main.c | 3 +--
2 files changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/base/power/clock_ops.c b/drivers/base/power/clock_ops.c
index 59bb37e8244c..1f708e10e711 100644
--- a/drivers/base/power/clock_ops.c
+++ b/drivers/base/power/clock_ops.c
@@ -422,13 +422,11 @@ void pm_clk_destroy(struct device *dev)
{
struct pm_subsys_data *psd = dev_to_psd(dev);
struct pm_clock_entry *ce, *c;
- struct list_head list;
+ LIST_HEAD(list);
if (!psd)
return;
- INIT_LIST_HEAD(&list);
-
pm_clk_list_lock(psd);
list_for_each_entry_safe_reverse(ce, c, &psd->clock_list, node)
diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
index e1b550664bab..d0c7b1d4101e 100644
--- a/drivers/base/power/main.c
+++ b/drivers/base/power/main.c
@@ -1257,11 +1257,10 @@ static void device_complete(struct device *dev, pm_message_t state)
*/
void dpm_complete(pm_message_t state)
{
- struct list_head list;
+ LIST_HEAD(list);
trace_suspend_resume(TPS("dpm_complete"), state.event, true);
- INIT_LIST_HEAD(&list);
mutex_lock(&dpm_list_mtx);
while (!list_empty(&dpm_prepared_list)) {
struct device *dev = to_device(dpm_prepared_list.prev);
--
2.53.0
reply other threads:[~2026-05-19 6:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260519055920.13180-1-jszhang@kernel.org \
--to=jszhang@kernel.org \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@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