lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 19 Jul 2012 22:34:09 +0200 From: Carsten Emde <C.Emde@...dl.org> To: Rafael Wysocki <rjw@...k.pl> Cc: Deepthi Dharwar <deepthi@...ux.vnet.ibm.com>, Len Brown <len.brown@...el.com>, Kevin Hilman <khilman@...com>, Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, Linux PM mailing list <linux-pm@...r.kernel.org>, Carsten Emde <C.Emde@...dl.org> Subject: [PATCH 0/1 v3] cpuidle: allow to disable C states of the ladder governor 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists