From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Extra ACPI updates for v5.17-rc1
Date: Fri, 21 Jan 2022 20:25:34 +0100 [thread overview]
Message-ID: <CAJZ5v0gJkT+WwEe0=73HKek+B1Ko0XFtkFYbwxb3NBzjR-1=ng@mail.gmail.com> (raw)
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-5.17-rc1-3
with top-most commit f6f02040e0ca7cb2e82d8aeb8f7daf5d89acc04c
Merge branches 'acpi-cppc' and 'acpi-dptf'
on top of commit 6a8d7fbf1c65034b85e7676b42449a56e4206bd3
Merge tag 'acpi-5.17-rc1-2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
to receive extra ACPI updates for 5.17-rc1.
These fix and clean up the ACPI CPPC driver on top of the recent
changes in it merged previously and add some new device IDs to
the ACPI DPTF driver.
Specifics:
- Fix a recently introduced endianness-related issue in the ACPI
CPPC library and clean it up on top of that (Rafael Wysocki).
- Add new device IDs for the Raptor Lake SoC to the ACPI DPTF
driver (Srinivas Pandruvada).
Thanks!
---------------
Rafael J. Wysocki (2):
ACPI: CPPC: Fix up I/O port access in cpc_read()
ACPI: CPPC: Drop redundant local variable from cpc_read()
Srinivas Pandruvada (1):
ACPI: DPTF: Support Raptor Lake
---------------
drivers/acpi/cppc_acpi.c | 11 ++++++-----
drivers/acpi/dptf/dptf_pch_fivr.c | 1 +
drivers/acpi/dptf/dptf_power.c | 2 ++
drivers/acpi/dptf/int340x_thermal.c | 6 ++++++
drivers/acpi/fan.h | 1 +
5 files changed, 16 insertions(+), 5 deletions(-)
next reply other threads:[~2022-01-21 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 19:25 Rafael J. Wysocki [this message]
2022-01-22 9:40 ` [GIT PULL] Extra ACPI updates for v5.17-rc1 pr-tracker-bot
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='CAJZ5v0gJkT+WwEe0=73HKek+B1Ko0XFtkFYbwxb3NBzjR-1=ng@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).