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 changes for 5.2
Date: Mon, 29 Apr 2019 15:36:13 +0530 [thread overview]
Message-ID: <20190429100613.xuqm3mdxzrc2np6o@vireshk-i7> (raw)
Hi Rafael,
This pull request contains:
- Fix for possible object reference leak for few drivers (Wen Yang).
- Fix for armada frequency calculation (Gregory).
- Code cleanup in maple driver (Viresh).
This contains some non-ARM bits as well this time as the patches were
picked up from a series.
--
viresh
-------------------------8<-------------------------
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git cpufreq/arm/linux-next
for you to fetch changes up to 8db82563451f976597ab7b282ec655e4390a4088:
cpufreq: armada-37xx: fix frequency calculation for opp (2019-04-29 15:22:50 +0530)
----------------------------------------------------------------
Gregory CLEMENT (1):
cpufreq: armada-37xx: fix frequency calculation for opp
Viresh Kumar (1):
cpufreq: maple: Remove redundant code from maple_cpufreq_init()
Wen Yang (7):
cpufreq: ap806: fix possible object reference leak
cpufreq: imx6q: fix possible object reference leak
cpufreq: kirkwood: fix possible object reference leak
cpufreq: maple: fix possible object reference leak
cpufreq/pasemi: fix possible object reference leak
cpufreq: pmac32: fix possible object reference leak
cpufreq: ppc_cbe: fix possible object reference leak
drivers/cpufreq/armada-37xx-cpufreq.c | 22 +++++++++++++++++++---
drivers/cpufreq/armada-8k-cpufreq.c | 1 +
drivers/cpufreq/imx6q-cpufreq.c | 4 ++--
drivers/cpufreq/kirkwood-cpufreq.c | 19 +++++++++++--------
drivers/cpufreq/maple-cpufreq.c | 6 +-----
drivers/cpufreq/pasemi-cpufreq.c | 1 +
drivers/cpufreq/pmac32-cpufreq.c | 2 ++
drivers/cpufreq/ppc_cbe_cpufreq.c | 1 +
8 files changed, 38 insertions(+), 18 deletions(-)
next reply other threads:[~2019-04-29 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 10:06 Viresh Kumar [this message]
2019-04-30 10:14 ` [GIT PULL] cpufreq/arm changes for 5.2 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=20190429100613.xuqm3mdxzrc2np6o@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