From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
John Garry <john.garry@huawei.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v3] hisi_lpc: Use acpi_dev_for_each_child()
Date: Fri, 1 Jul 2022 10:34:56 +0200 [thread overview]
Message-ID: <Yr6xsKbZSMWywUKo@kroah.com> (raw)
In-Reply-To: <5606189.DvuYhMxLoT@kreacher>
On Thu, Jun 30, 2022 at 08:13:52PM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Subject: [PATCH] hisi_lpc: Use acpi_dev_for_each_child()
>
> 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).
>
> While at it, simplify hisi_lpc_acpi_set_io_res() by making it accept
> a struct acpi_device pointer from the caller, instead of going to
> struct device and back to get the same result, and clean up confusion
> regarding hostdev and its ACPI companion in that function.
>
> Also remove a redundant check from it.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2022-07-01 8:35 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 ` [PATCH v2] " Rafael J. Wysocki
2022-06-30 12:48 ` 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 [this message]
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=Yr6xsKbZSMWywUKo@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.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