linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	cpufreq@vger.kernel.org, kyungmin.park@samsung.com,
	myungjoo.ham@samsung.com
Subject: Re: [RESEND][PATCH] cpufreq: stats: Add 'load_table' sysfs file to show accumulated data of CPU
Date: Fri, 14 Jun 2013 14:48:27 +0200	[thread overview]
Message-ID: <8166789.M9n1Uisvhs@vostro.rjw.lan> (raw)
In-Reply-To: <CAKohpokL1PNsYXJvnrkYesUHhe4s9-HsZe_c5KW+toeHJep2PA@mail.gmail.com>

On Friday, June 14, 2013 09:41:13 AM Viresh Kumar wrote:
> On 14 June 2013 07:41, Chanwoo Choi <cw00.choi@samsung.com> wrote:
> > OK, I will reimplement load_table node by using debugfs instead of sysfs.
> 
> @Rafael: Would it be move trans_table to debugfs??

I'm not sure who uses it now.  If there are any user space tools depending on
it in use, I'm afraid we can't just move it around.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  reply	other threads:[~2013-06-14 12:39 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
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 [this message]
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=8166789.M9n1Uisvhs@vostro.rjw.lan \
    --to=rjw@sisk.pl \
    --cc=cpufreq@vger.kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --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 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).