From: Chanwoo Choi <cw00.choi@samsung.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, cpufreq@vger.kernel.org,
kyungmin.park@samsung.com, myungjoo.ham@samsung.com,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>
Subject: Re: [RESEND][PATCH] cpufreq: stats: Add 'load_table' sysfs file to show accumulated data of CPU
Date: Tue, 11 Jun 2013 15:10:55 +0900 [thread overview]
Message-ID: <51B6BF6F.2000902@samsung.com> (raw)
In-Reply-To: <CAKohpomNN=keppPeLLDor_6YpyOO19_fsbWZRE+w33DoVDBprw@mail.gmail.com>
On 06/11/2013 02:22 PM, Viresh Kumar wrote:
> On 11 June 2013 10:49, Chanwoo Choi <cw00.choi@samsung.com> wrote:
>> I will modify this patch according to your comment
>> and then resend it after merged below patch.
>> - [PATCH] cpufreq: stats: Remove CONFIG_CPU_FREQ_STAT_DETAILS
> Hmm.. Maybe you can sent it without rebasing your patch over mine and
> we can rebase it over my patch later. So, that you don't end up waiting for
> my patches to be included.
OK, I understand.
Thanks,
Chanwoo Choi
next prev parent reply other threads:[~2013-06-11 6:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 8:11 [RESEND][PATCH] cpufreq: stats: Add 'load_table' sysfs file to show accumulated data of CPU Chanwoo Choi
2013-06-07 10:23 ` Viresh Kumar
2013-06-10 12:13 ` Chanwoo Choi
2013-06-11 5:06 ` Viresh Kumar
2013-06-11 5:19 ` Chanwoo Choi
2013-06-11 5:22 ` Viresh Kumar
2013-06-11 6:10 ` Chanwoo Choi [this message]
2013-06-11 22:14 ` Rafael J. Wysocki
2013-06-12 0:51 ` Chanwoo Choi
2013-06-12 4:02 ` Viresh Kumar
2013-06-12 11:05 ` Rafael J. Wysocki
2013-06-14 2:11 ` Chanwoo Choi
2013-06-14 4:11 ` Viresh Kumar
2013-06-14 12:48 ` Rafael J. Wysocki
2013-06-14 14:49 ` Viresh Kumar
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=51B6BF6F.2000902@samsung.com \
--to=cw00.choi@samsung.com \
--cc=cpufreq@vger.kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=rjw@sisk.pl \
--cc=viresh.kumar@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.