From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Power management fixes for v5.6-rc2
Date: Fri, 14 Feb 2020 11:24:55 +0100 [thread overview]
Message-ID: <CAJZ5v0hpEebbSFUFdtRnLWvXhyruzNgNaL9o-Od1a3jkgYRQKg@mail.gmail.com> (raw)
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-5.6-rc2
with top-most commit 3629ac5b92535793ba6226e243c2324a20c35fae
Merge branch 'pm-cpufreq'
on top of commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9
Linux 5.6-rc1
to receive power management fixes for 5.6-rc2.
These fix issues related to the handling of wakeup events signaled
through the ACPI SCI while suspended to idle (Rafael Wysocki) and
unexport an internal cpufreq variable (Yangtao Li).
Thanks!
---------------
Rafael J. Wysocki (4):
ACPI: EC: Fix flushing of pending work
ACPI: PM: s2idle: Avoid possible race related to the EC GPE
ACPICA: Introduce acpi_any_gpe_status_set()
ACPI: PM: s2idle: Prevent spurious SCIs from waking up the system
Yangtao Li (1):
cpufreq: Make cpufreq_global_kobject static
---------------
drivers/acpi/acpica/achware.h | 2 ++
drivers/acpi/acpica/evxfgpe.c | 32 +++++++++++++++++++
drivers/acpi/acpica/hwgpe.c | 71 +++++++++++++++++++++++++++++++++++++++++++
drivers/acpi/ec.c | 44 ++++++++++++++++-----------
drivers/acpi/sleep.c | 50 ++++++++++++++++++++++--------
drivers/cpufreq/cpufreq.c | 5 ++-
include/acpi/acpixf.h | 1 +
include/linux/cpufreq.h | 3 --
include/linux/suspend.h | 2 +-
kernel/power/suspend.c | 9 +++---
10 files changed, 177 insertions(+), 42 deletions(-)
next reply other threads:[~2020-02-14 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 10:24 Rafael J. Wysocki [this message]
2020-02-14 21:40 ` [GIT PULL] Power management fixes for v5.6-rc2 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=CAJZ5v0hpEebbSFUFdtRnLWvXhyruzNgNaL9o-Od1a3jkgYRQKg@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).