From: "MyungJoo Ham" <myungjoo.ham@samsung.com>
To: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: "rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"lukasz.luba@arm.com" <lukasz.luba@arm.com>,
"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>
Subject: [PULL Request] Devfreq Fixes for RC5+.
Date: Tue, 21 Jun 2016 05:49:43 +0000 [thread overview]
Message-ID: <1787004839.214561.1466488183645.JavaMail.weblogic@ep2ml104d> (raw)
In-Reply-To: CGME20160621054943epcms1p5edf96fb3b2179a62bff867190bc6dc13@epcms1p5
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
Dear Rafael,
Here goes a pull request of "PM / Devfreq Fixes" targetting RC5+.
Cheers,
MyungJoo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e:
Linux 4.7-rc4 (2016-06-19 21:30:02 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git fixes
for you to fetch changes up to 72b2835bab6bb0f7688a78301ac1466c729cb1c9:
PM / devfreq: fix initialization of current frequency in last status (2016-06-21 14:25:30 +0900)
- ----------------------------------------------------------------
Pull Request of Devfreq Fixes (3.7 rc 5+) for Rafael Linux PM.
- ----------------------------------------------------------------
Cai Zhiyong (1):
PM / devfreq: fix double call put_device
Dan Carpenter (1):
PM / devfreq: exynos-nocp: Remove incorrect IS_ERR() check
Lukasz Luba (1):
PM / devfreq: fix initialization of current frequency in last status
MyungJoo Ham (3):
PM / devfreq: devm_kzalloc to have dev pointer more precisely
PM / devfreq: fix duplicated kfree on devfreq pointer
PM / devfreq: remove double put_device
drivers/devfreq/devfreq.c | 22 ++++++++++------------
drivers/devfreq/event/exynos-nocp.c | 3 ---
2 files changed, 10 insertions(+), 15 deletions(-)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJXaNMEAAoJEBOhurvWBoCK7zEQAJKBAEThlu6CdQEcN7duZE25
DD2pGzSKQ5sq/RYg6Y0BUcyY3ltgenRzv93OHyGs4k2Su65rRhso7ClKv6stWdUo
tfkWuvgH3Zjns0zllaknsCvl5izxRaYdCobmoDZ/omHvP3u9aLqbO7PAqonLQzX+
/mqasQV02GSBgsgJiS6t5hR68oBEmGMeS6yiZhM1BAPkVqvxVpopgNxY3ZFjHW+Y
IUzsleiivyU6hZjnJNwcRGJtq3uF+66YvDDM/7jUDAeDK1mFsmJo+kB9jTugLhvo
B6ZkOfgG+s3GRQYVlq61NHxcO5FQ8qDmDpBLaANeitd6IffVJoPoFusUWnTXcq5W
wxU/WOEgInRD2hb9yMTbzlFtJjSNPNM/yQSE7wSMFQgVIBoqVTL1ImWwfZKPhVCj
VNwibytPUJmZD2gT97Kzhnz7o0DDA/YlljYbmcj3L/yL+myltXKFsR998K80OiGk
byMehap5itfKmwU7WmgpUSCg2F0Kg9JcOAO8SR4J0RB39I1Uot5h6Hei6vbzf5al
R4VFYyNtk5VuMydtEFwm8m5HeK1TFQxZiGxMricD5U9sA4sODIrAWxDBA8wKMU87
y0rp3FPRUigPemzUIPXRSrwFpSltVFsdHt58/ZWLco1wTuV3bisbFP+qAwD9AwYr
L+atxnliyfnmn7OHvZxR
=BrZs
-----END PGP SIGNATURE-----
next parent reply other threads:[~2016-06-21 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160621054943epcms1p5edf96fb3b2179a62bff867190bc6dc13@epcms1p5>
2016-06-21 5:49 ` MyungJoo Ham [this message]
2016-06-21 22:26 ` [PULL Request] Devfreq Fixes for RC5+ Rafael J. Wysocki
2016-06-22 4:50 ` MyungJoo Ham
2016-06-23 2:23 ` MyungJoo Ham
2016-06-23 12:53 ` 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=1787004839.214561.1466488183645.JavaMail.weblogic@ep2ml104d \
--to=myungjoo.ham@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=myungjoo.ham@gmail.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
/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