From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH 1/2] ACPI: DPTF: Fix participant driver names
Date: Thu, 15 Oct 2020 12:47:07 -0700 [thread overview]
Message-ID: <1e820f96242cc847b8465751f074155f8e7b5819.camel@linux.intel.com> (raw)
In-Reply-To: <2071902.YaQf1D0BmN@kreacher>
On Thu, 2020-10-15 at 18:58 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> Change the names of DPTF participant drivers to adhere to the
> sysfs file naming conventions (no spaces present in the name in
> particular).
>
> Fixes: 2ce6324eadb0 ("ACPI: DPTF: Add PCH FIVR participant driver")
> Fixes: 6256ebd5daf9 ("ACPI / DPTF: Add DPTF power participant
> driver")
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> ---
> drivers/acpi/dptf/dptf_pch_fivr.c | 2 +-
> drivers/acpi/dptf/dptf_power.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux-pm/drivers/acpi/dptf/dptf_pch_fivr.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/dptf/dptf_pch_fivr.c
> +++ linux-pm/drivers/acpi/dptf/dptf_pch_fivr.c
> @@ -114,7 +114,7 @@ static struct platform_driver pch_fivr_d
> .probe = pch_fivr_add,
> .remove = pch_fivr_remove,
> .driver = {
> - .name = "DPTF PCH FIVR",
> + .name = "dptf_pch_fivr",
> .acpi_match_table = pch_fivr_device_ids,
> },
> };
> Index: linux-pm/drivers/acpi/dptf/dptf_power.c
> ===================================================================
> --- linux-pm.orig/drivers/acpi/dptf/dptf_power.c
> +++ linux-pm/drivers/acpi/dptf/dptf_power.c
> @@ -237,7 +237,7 @@ static struct platform_driver dptf_power
> .probe = dptf_power_add,
> .remove = dptf_power_remove,
> .driver = {
> - .name = "DPTF Platform Power",
> + .name = "dptf_power",
> .acpi_match_table = int3407_device_ids,
> },
> };
>
>
>
next prev parent reply other threads:[~2020-10-15 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 16:57 [PATCH 0/2] ACPI: DPTF: Driver name fixes and Kconfig update Rafael J. Wysocki
2020-10-15 16:58 ` [PATCH 1/2] ACPI: DPTF: Fix participant driver names Rafael J. Wysocki
2020-10-15 19:47 ` Srinivas Pandruvada [this message]
2020-10-16 8:23 ` Borislav Petkov
2020-10-15 16:59 ` [PATCH 2/2] ACPI: DPTF: Add ACPI_DPTF Kconfig menu Rafael J. Wysocki
2020-10-15 19:46 ` Srinivas Pandruvada
2020-10-16 8:25 ` Borislav Petkov
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=1e820f96242cc847b8465751f074155f8e7b5819.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=bp@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.