From: 함명주 <myungjoo.ham@samsung.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Randy Dunlap" <rdunlap@xenotime.net>,
"Nishanth Menon" <nm@ti.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rajagopal Venkat" <rajagopal.venkat@linaro.org>,
박경민 <kyungmin.park@samsung.com>, "Kevin Hilman" <khilman@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
이종화 <jonghwa3.lee@samsung.com>
Subject: Re: Re: [linux-next PATCH] PM / devfreq: documentation cleanups for devfreq header
Date: Wed, 31 Oct 2012 02:27:12 +0000 (GMT) [thread overview]
Message-ID: <29176137.554861351650430580.JavaMail.weblogic@epv6ml03> (raw)
> On Tuesday, October 30, 2012 08:09:09 AM MyungJoo Ham wrote:
[]
> >
> > Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
> >
> > Applying to git://git.kernel.org/pub/scm/linux/kernel/git/mzx/devfreq.git for-rafael, which is based on rafael's linux-pm.git / linux-next.
> >
> > http://git.kernel.org/?p=linux/kernel/git/mzx/devfreq.git;a=shortlog;h=refs/heads/for-rafael
> >
> > I'll apply your "Add sysfs node ..." patch after refactoring with Jonghwa's (devfreq trans_stat) as the two patches use the same data (list of available freqs).
>
> May I assume that you'll handle all of the subsequent devfreq patches too?
>
> Rafael
Yes, you may. I'll apply the patches (currently at http://git.kernel.org/?p=linux/kernel/git/mzx/devfreq.git;a=shortlog;h=refs/heads/for-rafael ) and send pull requests to you or Linus.
Anyway, do you want me to keep sending pull requests to you as you've told
last time?
Cheers,
MyungJoo
next reply other threads:[~2012-10-31 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 2:27 함명주 [this message]
2012-10-31 9:13 ` [linux-next PATCH] PM / devfreq: documentation cleanups for devfreq header Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 8:09 MyungJoo Ham
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=29176137.554861351650430580.JavaMail.weblogic@epv6ml03 \
--to=myungjoo.ham@samsung.com \
--cc=jonghwa3.lee@samsung.com \
--cc=khilman@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rajagopal.venkat@linaro.org \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
/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;
as well as URLs for NNTP newsgroup(s).