linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Power management fixes for v5.17-rc6
Date: Fri, 25 Feb 2022 16:32:00 +0100	[thread overview]
Message-ID: <CAJZ5v0jOz82pc7KvQrmBojyOAdL6tGnNtfqspROFf3j0+5enGA@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.17-rc6

with top-most commit c5eb92f57de2446e0071c3af70ea54f237eb05d5

 Merge branch 'cpufreq/arm/fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm

on top of commit cfb92440ee71adcc2105b0890bb01ac3cddb8507

 Linux 5.17-rc5

to receive power management fixes for 5.17-rc6.

These fix the throttle IRQ handling during cpufreq initialization on
Qualcomm platforms (Bjorn Andersson).

Thanks!


---------------

Bjorn Andersson (2):
      cpufreq: Reintroduce ready() callback
      cpufreq: qcom-hw: Delay enabling throttle_irq

---------------

 Documentation/cpu-freq/cpu-drivers.rst                    |  3 +++
 Documentation/translations/zh_CN/cpu-freq/cpu-drivers.rst |  2 ++
 drivers/cpufreq/cpufreq.c                                 |  4 ++++
 drivers/cpufreq/qcom-cpufreq-hw.c                         | 11 ++++++++++-
 include/linux/cpufreq.h                                   |  3 +++
 5 files changed, 22 insertions(+), 1 deletion(-)

             reply	other threads:[~2022-02-25 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 15:32 Rafael J. Wysocki [this message]
2022-02-25 20:44 ` [GIT PULL] Power management fixes for v5.17-rc6 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=CAJZ5v0jOz82pc7KvQrmBojyOAdL6tGnNtfqspROFf3j0+5enGA@mail.gmail.com \
    --to=rafael@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).