cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saravana Kannan <skannan@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Todd Poynor <toddpoynor@google.com>,
	"Srivatsa S. Bhat" <srivatsa@mit.edu>,
	"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
	Linux PM mailing list <linux-pm@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Ruchi Kandoi <kandoiruchi@google.com>
Subject: Re: RFC: Leave sysfs nodes alone during hotplug
Date: Wed, 09 Jul 2014 19:40:05 -0700	[thread overview]
Message-ID: <53BDFD05.9020000@codeaurora.org> (raw)
In-Reply-To: <CAKohpon968V4WF76frJOm=Y2Ses22GMrWLWNO4NaafYbvMZsXQ@mail.gmail.com>

On 07/07/2014 09:21 PM, Viresh Kumar wrote:
> On 8 July 2014 09:00,  <skannan@codeaurora.org> wrote:
>> Looks like there's enough interest. I'll also try to send out a patch of
>> what I think a simplified CPUfreq should look like.
>
> Okay, will wait for it then.
>

Sent a super preliminary version to give an idea of what I'm going for. 
Future patches would be replies to that thread.

-Saravana

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2014-07-10  2:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 21:59 RFC: Leave sysfs nodes alone during hotplug Saravana Kannan
2014-07-07 11:01 ` Viresh Kumar
2014-07-07 19:30   ` Saravana Kannan
2014-07-07 22:40     ` Todd Poynor
2014-07-08  1:18       ` Saravana Kannan
2014-07-08  2:40       ` Viresh Kumar
2014-07-08  3:30         ` skannan
2014-07-08  4:21           ` Viresh Kumar
2014-07-10  2:40             ` Saravana Kannan [this message]
2014-07-08  2:36     ` 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=53BDFD05.9020000@codeaurora.org \
    --to=skannan@codeaurora.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=kandoiruchi@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=srivatsa@mit.edu \
    --cc=toddpoynor@google.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).