From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Brownell <david-b@pacbell.net>,
linux-pm@lists.linux-foundation.org,
mark gross <640e9920@gmail.com>,
Florian Mickler <florian@mickler.org>, Neil Brown <neilb@suse.de>,
linux-pci@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Arve@smtp1.linux-foundation.org
Subject: Re: [linux-pm] [PATCH] PM: Make it possible to avoid wakeup events from being lost
Date: Sat, 26 Jun 2010 20:21:42 +0200 [thread overview]
Message-ID: <201006262021.42966.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1006261258140.22018-100000@netrider.rowland.org>
On Saturday, June 26, 2010, Alan Stern wrote:
> On Sat, 26 Jun 2010, David Brownell wrote:
...
> > > + The
> > > /sys/power/wakeup_count file allows user space to avoid
> > > + losing wakeup events
> > > when transitioning the system into a sleep
> > > + state. Reading
>
> This could have been phrased better: The /sys/power/wakeup_count file
> allows user space to put the system into a sleep state conditionally
> subject to the arrival of concurrent wakeup events, which will either
> block the sleep transition or cause it to fail.
I'll chage this in the final version. Thanks!
Rafael
next prev parent reply other threads:[~2010-06-26 18:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 16:54 David Brownell
2010-06-26 17:14 ` Alan Stern
2010-06-26 18:21 ` Rafael J. Wysocki [this message]
2010-06-26 19:58 ` Alan Stern
2010-06-27 2:43 ` David Brownell
2010-06-27 3:06 ` Alan Stern
2010-06-26 18:20 ` Rafael J. Wysocki
2010-06-27 23:59 Rafael J. Wysocki
2010-06-28 23:28 ` [linux-pm] " David Brownell
2010-06-29 19:57 ` Alan Stern
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=201006262021.42966.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=640e9920@gmail.com \
--cc=Arve@smtp1.linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=dmitry.torokhov@gmail.com \
--cc=florian@mickler.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=neilb@suse.de \
--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
all inboxes | Powered by JetHome®