From: "Doug Smythies" <dsmythies@telus.net>
To: "'Rafael J. Wysocki'" <rafael@kernel.org>
Cc: "'Rafael J. Wysocki'" <rjw@rjwysocki.net>,
'Thomas Gleixner' <tglx@linutronix.de>,
'Frederic Weisbecker' <fweisbec@gmail.com>,
'Paul McKenney' <paulmck@linux.vnet.ibm.com>,
'Thomas Ilsche' <thomas.ilsche@tu-dresden.de>,
'Rik van Riel' <riel@surriel.com>,
'Aubrey Li' <aubrey.li@linux.intel.com>,
'Mike Galbraith' <mgalbraith@suse.de>,
'LKML' <linux-kernel@vger.kernel.org>,
'Linux PM' <linux-pm@vger.kernel.org>,
'Peter Zijlstra' <peterz@infradead.org>,
'Doug Smythies' <dsmythies@telus.net>
Subject: RE: [RFC/RFT][PATCH v2 0/6] sched/cpuidle: Idle loop rework
Date: Thu, 8 Mar 2018 07:18:54 -0800 [thread overview]
Message-ID: <000a01d3b6f0$c870d380$59527a80$@net> (raw)
In-Reply-To: tkIhevBcspApstkMJea2ob
On 2018.03.07 17:29 Doug wrote:
> On 2018.03.07 14:12 Rafael J. Wysocki wrote:
>> On Wed, Mar 7, 2018 at 6:04 PM, Doug Smythies <dsmythies@telus.net> wrote:
>>> On 2018.03.06 12:57 Rafael J. Wysocki wrote:
>>
>>> During the test I got some messages (I also got some with the V1 patch set):
>
>> Can you please check if that's reporoducible with just the first three
>> patches in the series applied?
>
> I will.
No issues. Test duration: 7 hours and 26 minutes.
Boot seems normal. Times re-booted 4.
... Doug
next prev parent reply other threads:[~2018-03-08 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 17:04 [RFC/RFT][PATCH v2 0/6] sched/cpuidle: Idle loop rework Doug Smythies
2018-03-07 22:11 ` Rafael J. Wysocki
2018-03-08 1:28 ` Doug Smythies
2018-03-08 15:18 ` Doug Smythies [this message]
2018-03-08 16:16 ` Rik van Riel
2018-03-08 16:36 ` Rafael J. Wysocki
2018-03-08 16:37 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 8:57 Rafael J. Wysocki
2018-03-08 10:31 ` Mike Galbraith
2018-03-08 11:10 ` Rafael J. Wysocki
2018-03-08 13:40 ` Mike Galbraith
2018-03-09 9:58 ` Rafael J. Wysocki
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='000a01d3b6f0$c870d380$59527a80$@net' \
--to=dsmythies@telus.net \
--cc=aubrey.li@linux.intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mgalbraith@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=riel@surriel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
--cc=thomas.ilsche@tu-dresden.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 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.