From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>
Subject: [GIT PULL] cpufreq/arm fixes for 5.18-rc5
Date: Tue, 26 Apr 2022 12:22:39 +0530 [thread overview]
Message-ID: <20220426065239.qtho7kwvdohqnff2@vireshk-i7> (raw)
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git tags/cpufreq-arm-fixes-5.18-rc5
for you to fetch changes up to e4e6448638a01905faeda9bf96aa9df7c8ef463c:
cpufreq: qcom-cpufreq-hw: Clear dcvs interrupts (2022-04-26 12:08:31 +0530)
----------------------------------------------------------------
cpufreq arm fixes for 5.18-rc5
- Fix issues with the Qualcomm's cpufreq driver (Dmitry Baryshkov and
Vladimir Zapolskiy).
- Fix memory leak with the Sun501 driver (Xiaobing Luo).
----------------------------------------------------------------
Dmitry Baryshkov (4):
cpufreq: qcom-hw: drop affinity hint before freeing the IRQ
cpufreq: qcom-hw: fix the race between LMH worker and cpuhp
cpufreq: qcom-hw: fix the opp entries refcounting
cpufreq: qcom-hw: provide online/offline operations
Vladimir Zapolskiy (2):
cpufreq: qcom-cpufreq-hw: Fix throttle frequency value on EPSS platforms
cpufreq: qcom-cpufreq-hw: Clear dcvs interrupts
Xiaobing Luo (1):
cpufreq: fix memory leak in sun50i_cpufreq_nvmem_probe
drivers/cpufreq/qcom-cpufreq-hw.c | 70 +++++++++++++++++++++++++++-------
drivers/cpufreq/sun50i-cpufreq-nvmem.c | 4 +-
2 files changed, 60 insertions(+), 14 deletions(-)
--
viresh
next reply other threads:[~2022-04-26 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 6:52 Viresh Kumar [this message]
2022-04-27 18:39 ` [GIT PULL] cpufreq/arm fixes for 5.18-rc5 Rafael J. Wysocki
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=20220426065239.qtho7kwvdohqnff2@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.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