From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] ACPI / property: use cached name in acpi_fwnode_get_named_child_node()
Date: Mon, 22 Jun 2020 17:46:46 +0200 [thread overview]
Message-ID: <2153046.FaeeqxahQX@kreacher> (raw)
In-Reply-To: <20200609132239.27272-1-heikki.krogerus@linux.intel.com>
On Tuesday, June 9, 2020 3:22:39 PM CEST Heikki Krogerus wrote:
> There is no need to re-evaluate the object name.
>
> Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> drivers/acpi/property.c | 14 ++------------
> 1 file changed, 2 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/acpi/property.c b/drivers/acpi/property.c
> index e601c4511a8b5..6941062272e0b 100644
> --- a/drivers/acpi/property.c
> +++ b/drivers/acpi/property.c
> @@ -606,13 +606,7 @@ static struct fwnode_handle *
> acpi_fwnode_get_named_child_node(const struct fwnode_handle *fwnode,
> const char *childname)
> {
> - char name[ACPI_PATH_SEGMENT_LENGTH];
> struct fwnode_handle *child;
> - struct acpi_buffer path;
> - acpi_status status;
> -
> - path.length = sizeof(name);
> - path.pointer = name;
>
> fwnode_for_each_child_node(fwnode, child) {
> if (is_acpi_data_node(child)) {
> @@ -621,12 +615,8 @@ acpi_fwnode_get_named_child_node(const struct fwnode_handle *fwnode,
> continue;
> }
>
> - status = acpi_get_name(ACPI_HANDLE_FWNODE(child),
> - ACPI_SINGLE_NAME, &path);
> - if (ACPI_FAILURE(status))
> - break;
> -
> - if (!strncmp(name, childname, ACPI_NAMESEG_SIZE))
> + if (!strncmp(acpi_device_bid(to_acpi_device_node(child)),
> + childname, ACPI_NAMESEG_SIZE))
> return child;
> }
>
>
Applied as 5.9 material, thanks!
prev parent reply other threads:[~2020-06-22 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 13:22 [PATCH] ACPI / property: use cached name in acpi_fwnode_get_named_child_node() Heikki Krogerus
2020-06-22 15:46 ` Rafael J. Wysocki [this message]
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=2153046.FaeeqxahQX@kreacher \
--to=rjw@rjwysocki.net \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@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