From: Viresh Kumar <viresh.kumar@linaro.org>
To: Saravana Kannan <skannan@codeaurora.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Doug Smythies <dsmythies@telus.net>,
"'Rafael J. Wysocki'" <rafael@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: System will not suspend with highest numbered CPU offline [REGRESSION][BISECTED]
Date: Tue, 13 Oct 2015 09:17:55 +0530 [thread overview]
Message-ID: <20151013034755.GS5386@linux> (raw)
In-Reply-To: <561C0D5A.1040008@codeaurora.org>
On 12-10-15, 12:43, Saravana Kannan wrote:
> Did I also convince you about allowing changing of parameters for
> offline CPUs? Which would also include inactive policies?
Yes, but that requires some careful modification of the code as there
are various paths of the sysfs write path. And we need to see that we
don't do anything more than just updating the files. So, I left it for
now.
--
viresh
next prev parent reply other threads:[~2015-10-13 3:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 21:40 System will not suspend with highest numbered CPU offline [REGRESSION][BISECTED] Doug Smythies
2015-09-04 14:59 ` Rafael J. Wysocki
2015-09-04 14:42 ` Viresh Kumar
2015-09-04 18:41 ` Doug Smythies
2015-09-04 22:26 ` Rafael J. Wysocki
2015-09-04 23:05 ` Doug Smythies
2015-09-05 0:22 ` Rafael J. Wysocki
2015-09-05 1:41 ` Rafael J. Wysocki
2015-09-05 2:34 ` Doug Smythies
2015-09-05 7:46 ` Doug Smythies
2015-09-05 8:14 ` Viresh Kumar
2015-09-07 13:32 ` Rafael J. Wysocki
2015-09-08 2:40 ` Viresh Kumar
2015-09-11 20:43 ` Saravana Kannan
2015-09-11 21:30 ` Rafael J. Wysocki
2015-09-11 22:07 ` Saravana Kannan
2015-10-11 9:47 ` Viresh Kumar
2015-10-12 19:43 ` Saravana Kannan
2015-10-13 3:47 ` Viresh Kumar [this message]
2015-10-13 19:23 ` Saravana Kannan
2015-09-07 13:07 ` Rafael J. Wysocki
2015-09-07 14:03 ` Doug Smythies
2015-09-07 20:35 ` Rafael J. Wysocki
2015-09-04 15:26 ` Doug Smythies
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=20151013034755.GS5386@linux \
--to=viresh.kumar@linaro.org \
--cc=dsmythies@telus.net \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=skannan@codeaurora.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).