From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751715Ab2GSUuV (ORCPT ); Thu, 19 Jul 2012 16:50:21 -0400 Received: from toro.web-alm.net ([62.245.132.31]:58312 "EHLO toro.web-alm.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751134Ab2GSUuT (ORCPT ); Thu, 19 Jul 2012 16:50:19 -0400 Message-Id: <20120719203409.398114351@osadl.org> User-Agent: quilt/0.51-1 Date: Thu, 19 Jul 2012 22:34:09 +0200 From: Carsten Emde To: Rafael Wysocki Cc: Deepthi Dharwar , Len Brown , Kevin Hilman , Thomas Gleixner , LKML , Linux PM mailing list , Carsten Emde Subject: [PATCH 0/1 v3] cpuidle: allow to disable C states of the ladder governor References: <201207192130.20520.rjw@sisk.pl> <201207192042.57935.rjw@sisk.pl> <20120719185212.184458166@osadl.org> <20120719190740.215034590@osadl.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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.