From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
john.garry@huawei.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [PATCH v2] hisi_lpc: Use acpi_dev_for_each_child()
Date: Wed, 29 Jun 2022 15:47:21 +0200 [thread overview]
Message-ID: <2657553.mvXUDI8C0e@kreacher> (raw)
In-Reply-To: <12026357.O9o76ZdvQC@kreacher>
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Instead of walking the list of children of an ACPI device directly,
use acpi_dev_for_each_child() to carry out an action for all of
the given ACPI device's children.
This will help to eliminate the children list head from struct
acpi_device as it is redundant and it is used in questionable ways
in some places (in particular, locking is needed for walking the
list pointed to it safely, but it is often missing).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: John Garry <john.garry@huawei.com>
---
-> v2:
* Drop unused local variable (John).
* Add ACK from John.
---
drivers/bus/hisi_lpc.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
Index: linux-pm/drivers/bus/hisi_lpc.c
===================================================================
--- linux-pm.orig/drivers/bus/hisi_lpc.c
+++ linux-pm/drivers/bus/hisi_lpc.c
@@ -471,6 +471,12 @@ static int hisi_lpc_acpi_remove_subdev(s
return 0;
}
+static int hisi_lpc_acpi_clear_enumerated(struct acpi_device *adev, void *not_used)
+{
+ acpi_device_clear_enumerated(adev);
+ return 0;
+}
+
struct hisi_lpc_acpi_cell {
const char *hid;
const char *name;
@@ -480,13 +486,9 @@ struct hisi_lpc_acpi_cell {
static void hisi_lpc_acpi_remove(struct device *hostdev)
{
- struct acpi_device *adev = ACPI_COMPANION(hostdev);
- struct acpi_device *child;
-
device_for_each_child(hostdev, NULL, hisi_lpc_acpi_remove_subdev);
-
- list_for_each_entry(child, &adev->children, node)
- acpi_device_clear_enumerated(child);
+ acpi_dev_for_each_child(ACPI_COMPANION(hostdev),
+ hisi_lpc_acpi_clear_enumerated, NULL);
}
/*
next prev parent reply other threads:[~2022-06-29 13:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:55 [PATCH] hisi_lpc: Use acpi_dev_for_each_child() Rafael J. Wysocki
2022-06-29 13:33 ` John Garry
2022-06-29 13:38 ` Rafael J. Wysocki
2022-06-29 13:47 ` Rafael J. Wysocki [this message]
2022-06-30 12:48 ` [PATCH v2] " Rafael J. Wysocki
2022-06-30 13:37 ` John Garry
2022-06-30 13:40 ` Rafael J. Wysocki
2022-06-30 18:13 ` [PATCH v3] " Rafael J. Wysocki
2022-07-01 8:34 ` Greg Kroah-Hartman
2022-07-01 10:49 ` John Garry
2022-07-01 11:06 ` Andy Shevchenko
2022-07-01 11:07 ` Andy Shevchenko
2022-07-01 11:54 ` John Garry
2022-07-01 12:05 ` Andy Shevchenko
2022-07-01 12:18 ` John Garry
2022-07-04 19:02 ` Rafael J. Wysocki
2022-07-05 8:37 ` John Garry
2022-07-05 9:38 ` Andy Shevchenko
2022-07-05 9:39 ` Andy Shevchenko
2022-07-05 10:16 ` John Garry
2022-07-05 10:29 ` Andy Shevchenko
2022-07-05 13:54 ` Rafael J. Wysocki
2022-07-05 15:16 ` John Garry
2022-07-05 15:34 ` Rafael J. Wysocki
2022-08-09 10:35 ` John Garry
2022-07-05 15:08 ` Rafael J. Wysocki
2022-07-01 18:16 ` Rafael J. Wysocki
2022-07-01 18:19 ` Rafael J. Wysocki
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=2657553.mvXUDI8C0e@kreacher \
--to=rjw@rjwysocki.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.garry@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.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