linux-kernel - [GIT PULL] More power management fixes for 2.6.37

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <201011170011.46080.rjw@sisk.pl>
Date:	Wed, 17 Nov 2010 00:11:45 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	LKML <linux-kernel@...r.kernel.org>,
	"Linux-pm mailing list" <linux-pm@...ts.linux-foundation.org>
Subject: [GIT PULL] More power management fixes for 2.6.37

Hi Linus,

Please pull a few more power management fixes for 2.6.37 from:

git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6.git pm-fixes

They include:

* Fix for an embarassing bug in PM QoS.

* Change disabling the OPPs API on configurations that don't support OPPs.

* PM core modification allowing devices to be unregistered during late
  suspend and early resume (you've seen it already).


 Documentation/power/opp.txt |    3 +++
 drivers/base/power/main.c   |   34 ++++++++++++++++++++++++++++++----
 kernel/pm_qos_params.c      |    4 ++--
 kernel/power/Kconfig        |    4 ++++
 4 files changed, 39 insertions(+), 6 deletions(-)

---------------

Colin Cross (1):
      PM / PM QoS: Fix reversed min and max

Mark Brown (1):
      PM / OPP: Hide OPP configuration when SoCs do not provide an implementation

Rafael J. Wysocki (1):
      PM: Allow devices to be removed during late suspend and early resume

--
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/