From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
Cc: Rafael Wysocki <rafael.j.wysocki@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Zhang, Rui" <rui.zhang@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI: fan: fix: Update Tiger Lake ACPI device ID
Date: Tue, 30 Jun 2020 19:34:27 +0200 [thread overview]
Message-ID: <CAJZ5v0hkdDoed7ALMK+DR6h+qxnG3WXFsGMse5z+GcVpws8HPQ@mail.gmail.com> (raw)
In-Reply-To: <1593531709-21749-1-git-send-email-sumeet.r.pawnikar@intel.com>
[Cc linux-acpi]
On Tue, Jun 30, 2020 at 5:35 PM Sumeet Pawnikar
<sumeet.r.pawnikar@intel.com> wrote:
>
> Tiger Lake's new unique ACPI device ID for Fan is not valid
> because of missing 'C' in the ID. Fix this Fan ID by updating it.
>
> Fixes: c248dfe7e0ca ("ACPI: fan: Add Tiger Lake ACPI device ID")
> Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> ---
> drivers/acpi/fan.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/fan.c b/drivers/acpi/fan.c
> index 873e039ad4b7..62873388b24f 100644
> --- a/drivers/acpi/fan.c
> +++ b/drivers/acpi/fan.c
> @@ -25,8 +25,8 @@
>
> static const struct acpi_device_id fan_device_ids[] = {
> {"PNP0C0B", 0},
> - {"INT1044", 0},
> {"INT3404", 0},
> + {"INTC1044", 0},
> {"", 0},
> };
> MODULE_DEVICE_TABLE(acpi, fan_device_ids);
> --
Applied as 5.8-rc material with some changelog and subject edits, thanks!
prev parent reply other threads:[~2020-06-30 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 15:41 [PATCH] ACPI: fan: fix: Update Tiger Lake ACPI device ID Sumeet Pawnikar
2020-06-30 17:34 ` 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=CAJZ5v0hkdDoed7ALMK+DR6h+qxnG3WXFsGMse5z+GcVpws8HPQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=sumeet.r.pawnikar@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).