From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
linux-sh@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [GIT PULL] More power management fixes for 3.0
Date: Wed, 22 Jun 2011 20:04:54 +0000 [thread overview]
Message-ID: <201106222204.54532.rjw@sisk.pl> (raw)
Hi Linus,
Please pull power management fixes for 3.0 from:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/suspend-2.6.git pm-fixes
They include:
* Power management documentation fixes updating information on things that have
changed.
* Fix for potential PCI PM regression related to interactions between system
suspend/hibernation and the runtime PM framework.
* Fix for smobile regression related to the management of device clocks when
CONFIG_PM_RUNTIME is unset.
* Fix for a long-standing issue in the async suspend error code path (accompanied
by a field rename in struct dev_pm_info).
* Fix for a long-standing hibernation bug related to its user space interface.
Documentation/power/devices.txt | 67 +++++++----------------------------
Documentation/power/runtime_pm.txt | 5 ---
drivers/base/power/clock_ops.c | 4 +-
drivers/base/power/main.c | 28 +++++++++++----
drivers/pci/pci-driver.c | 4 ++-
drivers/usb/core/driver.c | 6 ++--
include/linux/device.h | 4 +-
include/linux/pm.h | 3 +-
kernel/power/user.c | 4 ++-
9 files changed, 50 insertions(+), 75 deletions(-)
---------------
Alan Stern (2):
PM: Rename dev_pm_info.in_suspend to is_prepared
PM: Fix async resume following suspend failure
Kevin Hilman (1):
PM / Runtime: Update doc: usage count no longer incremented across system PM
Michal Kubecek (1):
PM: Free memory bitmaps if opening /dev/snapshot fails
Rafael J. Wysocki (4):
PM: Update documentation regarding sysdevs
PM / Runtime: Handle clocks correctly if CONFIG_PM_RUNTIME is unset
PM / Domains: Update documentation
PCI / PM: Block races between runtime PM and system sleep
reply other threads:[~2011-06-22 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201106222204.54532.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-sh@vger.kernel.org \
--cc=torvalds@linux-foundation.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