From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: 최찬우 <cw00.choi@samsung.com>, "joe@perches.com" <joe@perches.com>,
박경민 <kyungmin.park@samsung.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Re: [PATCH v2 2/2] MAINTAINERS: Add devfreq-event entry
Date: Fri, 06 Nov 2015 00:27:17 +0000 (GMT) [thread overview]
Message-ID: <691485357.124481446769636099.JavaMail.weblogic@ep2mlwas05c> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1376 bytes --]
>On Thursday, November 05, 2015 11:37:59 PM MyungJoo Ham wrote:
>> >On Thursday, November 05, 2015 06:53:13 AM MyungJoo Ham wrote:
>> >> >
>> >> > This patch adds the devfreq-event[1] entry to review the patches
>> >> > as just supporter. Patches will be picked up by Myungjoo Ham on
>> >> > devfreq git repository.
>> >> > [1] https://lkml.org/lkml/2015/1/25/573
>> >> >
>> >> > Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>> >>
>> >> Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
>> >
>> >Well, does this mean I'm supposed to apply the patch directly?
>> >
>> >Or can you please do that?
>> >
>> >Rafael
>>
>> That means that I'll be getting patches from Chanwoo and
>> merge with the rest of devfreq in my repo first before
>> going out.
>
>Cool, thanks!
>
>I'll be waiting for a pull request from you, then.
>
>But can you please send it to me early next week (preferably on Monday),
>so I can include it into my next pull request for Linus?
Don'y worry; there are no patches to pull right now.
The patches in the link, [1] https://lkml.org/lkml/2015/1/25/573,
are already in the tree. That link only demonstrates what is
`devfreq-event' being added to /MAINTAINERS.
Cheers,
MyungJoo
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2015-11-06 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 0:27 MyungJoo Ham [this message]
2015-11-25 11:11 ` Chanwoo Choi
-- strict thread matches above, loose matches on Subject: below --
2015-11-05 23:37 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=691485357.124481446769636099.JavaMail.weblogic@ep2mlwas05c \
--to=myungjoo.ham@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=joe@perches.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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
all inboxes | Powered by JetHome®