From: Nishanth Menon <nm@ti.com>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rafael.j.wysocki@intel.com>, <rajagopal.venkat@linaro.org>,
<a.kesavan@samsung.com>, <jonghwa3.lee@samsung.com>,
<sangjung.woo@samsung.com>, <myungjoo.ham@gmail.com>
Subject: Re: [PATCH] PM / devfreq: add comments and Documentation
Date: Tue, 5 Feb 2013 09:02:58 -0600 [thread overview]
Message-ID: <20130205150258.GA7454@kahuna> (raw)
In-Reply-To: <1360057555-10279-1-git-send-email-myungjoo.ham@samsung.com>
On 18:45-20130205, MyungJoo Ham wrote:
> - Added missing ABI documents
> - Added comments to clarify the objectives of functions
>
> Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Acked-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-02-05 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 9:45 [PATCH] PM / devfreq: add comments and Documentation MyungJoo Ham
2013-02-05 15:02 ` Nishanth Menon [this message]
2013-02-05 15:41 ` Rajagopal Venkat
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=20130205150258.GA7454@kahuna \
--to=nm@ti.com \
--cc=a.kesavan@samsung.com \
--cc=jonghwa3.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rajagopal.venkat@linaro.org \
--cc=sangjung.woo@samsung.com \
/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