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] ACPI fixes for v6.0-rc3
Date: Sat, 27 Aug 2022 15:39:30 +0200 [thread overview]
Message-ID: <CAJZ5v0jnkSjtMff7uEKTCHLENMJYDd26BEjjZ3XK7fZMxHtd=Q@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-6.0-rc3
with top-most commit 2413a85200ee9cbed40d12c6e3b856752b089790
Merge branch 'acpi-processor' into acpi
on top of commit 1c23f9e627a7b412978b4e852793c5e3c3efc555
Linux 6.0-rc2
to receive ACPI fixes for 6.0-rc3.
These fix issues introduced by recent changes related to the handling of
ACPI device properties and a coding mistake in the exit path of the ACPI
processor driver.
Specifics:
- Prevent acpi_thermal_cpufreq_exit() from attempting to remove
the same frequency QoS request for multiple times (Riwen Lu).
- Fix type detection for integer ACPI device properties (Stefan
Binding).
- Avoid emitting false-positive warnings when processing ACPI
device properties and drop the useless default case from the
acpi_copy_property_array_uint() macro (Sakari Ailus).
Thanks!
---------------
Riwen Lu (1):
ACPI: processor: Remove freq Qos request for all CPUs
Sakari Ailus (2):
ACPI: property: Ignore already existing data node tags
ACPI: property: Remove default association from integer maximum values
Stefan Binding (1):
ACPI: property: Fix type detection of unified integer reading functions
---------------
drivers/acpi/processor_thermal.c | 2 +-
drivers/acpi/property.c | 11 +++++------
2 files changed, 6 insertions(+), 7 deletions(-)
next reply other threads:[~2022-08-27 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 13:39 Rafael J. Wysocki [this message]
2022-08-27 23:07 ` [GIT PULL] ACPI fixes for v6.0-rc3 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='CAJZ5v0jnkSjtMff7uEKTCHLENMJYDd26BEjjZ3XK7fZMxHtd=Q@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).