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.3-rc2
Date: Thu, 25 Jul 2019 11:26:29 +0200 [thread overview]
Message-ID: <CAJZ5v0h5ZR9EhER_J1Qn9PJL-OAWbFvUb1rjTJkBg22p+Db6Kg@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.3-rc2
with top-most commit fdc75701578269f6931975aebf4069d9d8c77d34
Merge branch 'pm-cpufreq'
on top of commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b
Linus 5.3-rc1
to receive power management fixes for 5.3-rc2.
These fix two issues related to the RAPL MMIO interface support
added recently and one cpufreq driver issue.
Specifics:
- Initialize the power capping subsystem and the RAPL driver earlier
in case the int340X thermal driver is built-in and attempts to
register an MMIO interface for RAPL which must not happen before
the requisite infrastructure is ready (Zhang Rui).
- Fix the int340X thermal driver's RAPL MMIO interface registration
error path (Rafael Wysocki).
- Fix possible use-after-free in the pasemi cpufreq driver (Wen Yang).
Thanks!
---------------
Rafael J. Wysocki (1):
int340X/processor_thermal_device: Fix proc_thermal_rapl_remove()
Wen Yang (1):
cpufreq/pasemi: fix use-after-free in pas_cpufreq_cpu_init()
Zhang Rui (1):
powercap: Invoke powercap_init() and rapl_init() earlier
---------------
drivers/cpufreq/pasemi-cpufreq.c | 23 +++++++++-------------
drivers/powercap/intel_rapl_common.c | 2 +-
drivers/powercap/powercap_sys.c | 2 +-
.../int340x_thermal/processor_thermal_device.c | 4 ++++
4 files changed, 15 insertions(+), 16 deletions(-)
next reply other threads:[~2019-07-25 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:26 Rafael J. Wysocki [this message]
2019-07-25 16:25 ` [GIT PULL] Power management fixes for v5.3-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=CAJZ5v0h5ZR9EhER_J1Qn9PJL-OAWbFvUb1rjTJkBg22p+Db6Kg@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).