From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
mingo@elte.hu, amit.kucheria@linaro.org,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] sched: idle: Encapsulate the code to compile it out
Date: Fri, 6 Jun 2014 10:09:03 +0200 [thread overview]
Message-ID: <20140606080903.GS6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <8539453.ED7vQGf2Gc@vostro.rjw.lan>
[-- Attachment #1: Type: text/plain, Size: 320 bytes --]
On Fri, May 02, 2014 at 05:32:25PM +0200, Rafael J. Wysocki wrote:
> That would be perfectly fine by me, but I'm not sure what Ingo and Peter think
> about that.
>
> I can set up a branch with sched/idle/cpuidle changes.
Ingo typically likes things like that. I'm still a git Luddite, I'll
learn someday :-)
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-06-06 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 12:01 [PATCH V2 1/2] sched: idle: Encapsulate the code to compile it out Daniel Lezcano
2014-04-30 12:01 ` [PATCH V2 2/2] sched: idle: Store the idle state the cpu is Daniel Lezcano
2014-04-30 22:47 ` [PATCH V2 1/2] sched: idle: Encapsulate the code to compile it out Rafael J. Wysocki
2014-04-30 22:56 ` Rafael J. Wysocki
2014-05-02 8:59 ` Daniel Lezcano
2014-05-02 12:09 ` Rafael J. Wysocki
2014-05-02 13:29 ` Daniel Lezcano
2014-05-02 18:20 ` Nicolas Pitre
2014-05-02 8:52 ` Daniel Lezcano
2014-05-02 12:09 ` Rafael J. Wysocki
2014-05-02 13:35 ` Daniel Lezcano
2014-05-02 15:32 ` Rafael J. Wysocki
2014-06-06 8:09 ` Peter Zijlstra [this message]
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=20140606080903.GS6758@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--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