From: John Garry <john.garry@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] hisi_lpc: Use acpi_dev_for_each_child()
Date: Thu, 30 Jun 2022 14:37:14 +0100 [thread overview]
Message-ID: <7aad2916-1774-76c5-339a-bbcac4655642@huawei.com> (raw)
In-Reply-To: <CAJZ5v0jNOsAXSuX9dw9N3w12Y_nq62Z=OL4QQTwH=OnReGpQvA@mail.gmail.com>
On 30/06/2022 13:48, Rafael J. Wysocki wrote:
> On Wed, Jun 29, 2022 at 3:47 PM Rafael J. Wysocki <rjw@rjwysocki.net> wrote:
>>
>> 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).
>
> I've overlooked another usage of the children list in hisi_lpc, in
> hisi_lpc_acpi_probe(), and eliminating that one is a bit more
> complicated.
>
> So please scratch this one and I will send a v3 when 0-day tells me
> that it builds.
Hi Rafael,
If it makes things simpler then I can just fix the driver so that we
can't unload it. Let me know if that suits better.
Cheers
>
>> 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-30 13:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:55 [PATCH] " Rafael J. Wysocki
2022-06-29 13:33 ` John Garry
2022-06-29 13:38 ` Rafael J. Wysocki
2022-06-29 13:47 ` [PATCH v2] " Rafael J. Wysocki
2022-06-30 12:48 ` Rafael J. Wysocki
2022-06-30 13:37 ` John Garry [this message]
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=7aad2916-1774-76c5-339a-bbcac4655642@huawei.com \
--to=john.garry@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®