From: Carsten Emde <C.Emde@osadl.org>
To: Rafael Wysocki <rjw@sisk.pl>
Cc: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
Len Brown <len.brown@intel.com>, Kevin Hilman <khilman@ti.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>,
Carsten Emde <C.Emde@osadl.org>
Subject: [PATCH 0/1 v3] cpuidle: allow to disable C states of the ladder governor
Date: Thu, 19 Jul 2012 22:34:09 +0200 [thread overview]
Message-ID: <20120719203409.398114351@osadl.org> (raw)
In-Reply-To: <20120719190740.215034590@osadl.org>
Rafael,
> Your patch doesn't seem to take this linux-next commit:
> http://git.kernel.org/?p=linux/kernel/git/rafael/linux-pm.git;a=commit;h=dc7fd275ae60ef8edf952aff2a62462f5d892fd4
> into account, does it?
Hmm, oops, you're right. This one came in after I checked it last time.
Changes in v2: A note in the documentation explains why the sysfs
variable "disable" may not always reflect the current situation
and why modifying it may not always work as expected.
Changes in v3: The patch now applies to the current linux-next and
uses the per-cpu "disable" field.
-Carsten.
next prev parent reply other threads:[~2012-07-19 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 18:59 [PATCH 0/1] " Carsten Emde
2012-07-17 18:59 ` [PATCH 1/1] Honor state disabling in the cpuidle " Carsten Emde
2012-07-18 6:36 ` Deepthi Dharwar
2012-07-18 11:02 ` Carsten Emde
2012-07-18 11:48 ` Deepthi Dharwar
2012-07-18 14:09 ` [PATCH 1/1 v2] Honor state disabling in the cpuidle ladder governor - documented Carsten Emde
2012-07-18 14:38 ` [PATCH 1/1 v3] Honor state disabling in the cpuidle ladder governor - with sanitizer Carsten Emde
2012-07-19 11:14 ` Deepthi Dharwar
2012-07-19 11:39 ` Carsten Emde
2012-07-19 18:42 ` Rafael J. Wysocki
2012-07-19 18:52 ` [PATCH 0/1 v2] cpuidle: allow to disable C states of the ladder governor Carsten Emde
2012-07-19 18:52 ` [PATCH 1/1 v2] Honor state disabling in the cpuidle " Carsten Emde
2012-07-19 19:30 ` Rafael J. Wysocki
2012-07-19 20:34 ` Carsten Emde [this message]
2012-07-19 20:34 ` [PATCH 1/1 v3] " Carsten Emde
2012-07-19 21:48 ` Rafael J. Wysocki
2012-07-19 22:22 ` Carsten Emde
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=20120719203409.398114351@osadl.org \
--to=c.emde@osadl.org \
--cc=deepthi@linux.vnet.ibm.com \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--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
Powered by JetHome