From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] hwtracing: coresight: Replace acpi_bus_get_device()
Date: Wed, 2 Feb 2022 11:43:16 +0000 [thread overview]
Message-ID: <fca634ba-a05a-10e3-4c12-8774c49a91fe@arm.com> (raw)
In-Reply-To: <5790600.lOV4Wx5bFT@kreacher>
Hi Rafael
On 01/02/2022 17:58, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Replace acpi_bus_get_device() that is going to be dropped with
> acpi_fetch_acpi_dev().
>
> No intentional functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/hwtracing/coresight/coresight-platform.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> Index: linux-pm/drivers/hwtracing/coresight/coresight-platform.c
> ===================================================================
> --- linux-pm.orig/drivers/hwtracing/coresight/coresight-platform.c
> +++ linux-pm/drivers/hwtracing/coresight/coresight-platform.c
> @@ -626,7 +626,7 @@ static int acpi_coresight_parse_link(str
> const union acpi_object *link,
> struct coresight_connection *conn)
> {
> - int rc, dir;
> + int dir;
> const union acpi_object *fields;
> struct acpi_device *r_adev;
> struct device *rdev;
> @@ -643,9 +643,9 @@ static int acpi_coresight_parse_link(str
> fields[3].type != ACPI_TYPE_INTEGER)
> return -EINVAL;
>
> - rc = acpi_bus_get_device(fields[2].reference.handle, &r_adev);
> - if (rc)
> - return rc;
> + r_adev = acpi_fetch_acpi_dev(fields[2].reference.handle);
> + if (!r_adev)
> + return -ENODEV;
>
Is this patch part of a series ? I don't see acpi_fetch_acpi_dev()
in v5.17-rc1, which our tree is based on at the moment. Please could
you point us to the changes ?
Also do you expect to pull this via your tree ?
Cheers
Suzuki
> dir = fields[3].integer.value;
> if (dir == ACPI_CORESIGHT_LINK_MASTER) {
>
>
>
next prev parent reply other threads:[~2022-02-02 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 17:58 Rafael J. Wysocki
2022-02-02 11:43 ` Suzuki K Poulose [this message]
2022-02-02 13:44 ` Rafael J. Wysocki
2022-02-02 16:46 ` Suzuki K Poulose
2022-02-02 16:48 ` 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=fca634ba-a05a-10e3-4c12-8774c49a91fe@arm.com \
--to=suzuki.poulose@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=leo.yan@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.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®