From: Kevin Hilman <khilman@ti.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: MyungJoo Ham <myungjoo.ham@samsung.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-pm@lists.linux-foundation.org, Pavel Machek <pavel@ucw.cz>,
"Greg Kroah-Hartman" <gregkh@suse.de>, Nishanth Menon <nm@ti.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Colin Cross <ccross@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mike Turquette <mturquette@ti.com>,
myungjoo.ham@gmail.com
Subject: Re: [PATCH v13 0/4] Devfreq, DVFS Framework for Non-CPU Devices
Date: Fri, 30 Sep 2011 16:30:06 -0700 [thread overview]
Message-ID: <87wrcpehhd.fsf@ti.com> (raw)
In-Reply-To: <201109302244.37584.rjw@sisk.pl> (Rafael J. Wysocki's message of "Fri, 30 Sep 2011 22:44:37 +0200")
"Rafael J. Wysocki" <rjw@sisk.pl> writes:
> On Thursday, September 29, 2011, MyungJoo Ham wrote:
>> Summary of update from the patchset v12:
>>
>> - Bugfix: _remove_devfreq and devfreq_dev_release may be called multiple times.
>>
>> - Fixup kerneldoc comments.
>>
>> Reposting to LKML as Kernel-PM list seems broken.
>>
>> I didn't put Kevin's ACK at 2/4 patch as there has been changes in 2/4 patch
>> (the bugfix mentioned above).
Looks fine to me.
Rafael, feel free to add my Ack to 2/4 if you like.
Kevin
next prev parent reply other threads:[~2011-09-30 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 12:18 [PATCH v13 0/4] Devfreq, DVFS Framework for Non-CPU Devices MyungJoo Ham
2011-09-29 12:18 ` [PATCH v13 1/4] PM / OPP: Add OPP availability change notifier MyungJoo Ham
2011-09-29 12:18 ` [PATCH v13 2/4] PM: Introduce devfreq: generic DVFS framework with device-specific OPPs MyungJoo Ham
[not found] ` <4E85ADB7.1030900@gmail.com>
2011-09-30 16:41 ` Rafael J. Wysocki
2011-09-29 12:18 ` [PATCH v13 3/4] PM / devfreq: add common sysfs interfaces MyungJoo Ham
2011-09-29 12:18 ` [PATCH v13 4/4] PM / devfreq: add basic governors MyungJoo Ham
2011-09-30 20:44 ` [PATCH v13 0/4] Devfreq, DVFS Framework for Non-CPU Devices Rafael J. Wysocki
2011-09-30 23:30 ` Kevin Hilman [this message]
2011-10-01 22:26 ` 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=87wrcpehhd.fsf@ti.com \
--to=khilman@ti.com \
--cc=ccross@google.com \
--cc=gregkh@suse.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mturquette@ti.com \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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