From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Cc: <john.garry@huawei.com>
Subject: Re: [PATCH v1 4/4] bus: hisi_lpc: Don't guard ACPI IDs with ACPI_PTR()
Date: Tue, 5 Jul 2022 16:22:37 +0200 [thread overview]
Message-ID: <f1d1b9e3-fa4e-53a4-8971-d4e91c0c3ebf@intel.com> (raw)
In-Reply-To: <20220705114312.86164-4-andriy.shevchenko@linux.intel.com>
On 7/5/2022 1:43 PM, Andy Shevchenko wrote:
> The OF is not guarded neither ACPI needs. The IDs do not depend
> to the configuration. Hence drop ACPI_PTR() from the code and
> move ID table closer to its user.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> drivers/bus/hisi_lpc.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/bus/hisi_lpc.c b/drivers/bus/hisi_lpc.c
> index a6513a571d7b..74f4448bff9d 100644
> --- a/drivers/bus/hisi_lpc.c
> +++ b/drivers/bus/hisi_lpc.c
> @@ -589,11 +589,6 @@ static int hisi_lpc_acpi_probe(struct device *hostdev)
>
> return ret;
> }
> -
> -static const struct acpi_device_id hisi_lpc_acpi_match[] = {
> - {"HISI0191"},
> - {}
> -};
> #else
> static int hisi_lpc_acpi_probe(struct device *dev)
> {
> @@ -688,11 +683,16 @@ static const struct of_device_id hisi_lpc_of_match[] = {
> {}
> };
>
> +static const struct acpi_device_id hisi_lpc_acpi_match[] = {
> + {"HISI0191"},
> + {}
> +};
> +
> static struct platform_driver hisi_lpc_driver = {
> .driver = {
> .name = DRV_NAME,
> .of_match_table = hisi_lpc_of_match,
> - .acpi_match_table = ACPI_PTR(hisi_lpc_acpi_match),
> + .acpi_match_table = hisi_lpc_acpi_match,
> },
> .probe = hisi_lpc_probe,
> .remove = hisi_lpc_remove,
next prev parent reply other threads:[~2022-07-05 14:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 11:43 [PATCH v1 1/4] bus: hisi_lpc: Don't dereference fwnode handle Andy Shevchenko
2022-07-05 11:43 ` [PATCH v1 2/4] bus: hisi_lpc: Use devm_platform_ioremap_resource Andy Shevchenko
2022-07-05 14:38 ` Rafael J. Wysocki
2022-07-05 14:41 ` John Garry
2022-07-05 11:43 ` [PATCH v1 3/4] bus: hisi_lpc: Correct error code for timeout Andy Shevchenko
2022-07-05 14:39 ` Rafael J. Wysocki
2022-07-05 14:53 ` John Garry
2022-07-05 11:43 ` [PATCH v1 4/4] bus: hisi_lpc: Don't guard ACPI IDs with ACPI_PTR() Andy Shevchenko
2022-07-05 14:22 ` Rafael J. Wysocki [this message]
2022-07-05 14:51 ` John Garry
2022-07-05 15:15 ` Andy Shevchenko
2022-07-05 15:27 ` John Garry
2022-07-05 15:33 ` Andy Shevchenko
2022-07-05 14:17 ` [PATCH v1 1/4] bus: hisi_lpc: Don't dereference fwnode handle Rafael J. Wysocki
2022-07-05 15:02 ` John Garry
2022-07-05 15:23 ` Andy Shevchenko
2022-07-05 15:38 ` John Garry
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=f1d1b9e3-fa4e-53a4-8971-d4e91c0c3ebf@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=john.garry@huawei.com \
--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