From: James Hogan <james@albanarts.com>
To: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Randy Dunlap <rdunlap@xenotime.net>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
Alan Stern <stern@rowland.harvard.edu>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
markgross <markgross@thegnar.org>
Subject: [PATCH 0/2] pm_trace: Add locking and add sysfs attr for rechecking dev hash.
Date: Sat, 9 Oct 2010 23:34:27 +0100 [thread overview]
Message-ID: <201010092334.27808.james@albanarts.com> (raw)
A fix and an improvement to the pm_trace code.
The improvement allows finding out via sysfs which device was last traced when
the device is part of a kernel module (which means it doesn't get printed on
next boot since it isn't loaded yet).
Unsure as always about what to name stuff, so comments most welcome.
James Hogan (2):
pm_trace: Lock pm device list mutex.
pm_trace: Add sysfs attr for rechecking dev hash.
Documentation/power/s2ram.txt | 7 +++++++
drivers/base/power/trace.c | 32 +++++++++++++++++++++++++++++++-
include/linux/resume-trace.h | 2 ++
kernel/power/main.c | 18 ++++++++++++++++++
4 files changed, 58 insertions(+), 1 deletions(-)
--
1.7.2.3
next reply other threads:[~2010-10-09 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 22:34 James Hogan [this message]
2010-10-09 22:36 ` [PATCH 1/2] pm_trace: Lock pm device list mutex James Hogan
2010-10-09 22:43 ` Rafael J. Wysocki
2010-10-09 22:37 ` [PATCH 2/2] pm_trace: Add sysfs attr for rechecking dev hash James Hogan
2010-10-09 22:49 ` Rafael J. Wysocki
2010-10-09 23:13 ` James Hogan
2010-10-09 23:30 ` Rafael J. Wysocki
2010-10-10 18:04 ` Pavel Machek
2010-10-10 19:47 ` James Hogan
2010-10-10 20:47 ` Pavel Machek
2010-10-10 21:19 ` James Hogan
2010-10-10 22:12 ` Rafael J. Wysocki
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=201010092334.27808.james@albanarts.com \
--to=james@albanarts.com \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@xenotime.net \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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