From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Len Brown <lenb@kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
Eduardo Valentin <edubezval@gmail.com>,
Zhang Rui <rui.zhang@intel.com>, Petr Mladek <pmladek@suse.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH v4 1/2] idle: add support for tasks that inject idle
Date: Mon, 28 Nov 2016 16:39:48 -0800 [thread overview]
Message-ID: <20161128163948.28ff2fb8@icelake> (raw)
In-Reply-To: <20161128163307.7b5b7d68@icelake>
On Mon, 28 Nov 2016 16:33:07 -0800
Jacob Pan <jacob.jun.pan@linux.intel.com> wrote:
> > > + cpuidle_use_deepest_state(false);
> >
> > This actually depends on your [2/2], doesn't it?
>
> right, I shall put that after 2/2.
I mean reverse the order of the two patches. Should I resend the series
or you can reverse the order?
Thanks,
Jacob
next prev parent reply other threads:[~2016-11-29 0:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 21:33 [PATCH v4 0/2] Stop sched tick in idle injection task Jacob Pan
2016-11-28 21:33 ` [PATCH v4 1/2] idle: add support for tasks that inject idle Jacob Pan
2016-11-28 21:39 ` Rafael J. Wysocki
2016-11-28 21:46 ` Jacob Pan
2016-11-28 22:22 ` Rafael J. Wysocki
2016-11-28 23:18 ` kbuild test robot
2016-11-28 23:22 ` Rafael J. Wysocki
2016-11-29 0:33 ` Jacob Pan
2016-11-29 0:39 ` Jacob Pan [this message]
2016-11-29 0:45 ` Rafael J. Wysocki
2016-11-28 21:33 ` [PATCH v4 2/2] cpuidle: allow setting deepest idle Jacob Pan
2016-11-28 23:12 ` kbuild test robot
2016-11-28 23:19 ` Rafael J. Wysocki
2016-11-29 0:59 ` kbuild test robot
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=20161128163948.28ff2fb8@icelake \
--to=jacob.jun.pan@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=edubezval@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
/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