From: Valdis.Kletnieks@vt.edu
To: Pavel Machek <pavel@ucw.cz>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
Jouni Malinen <j@w1.fi>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stephen Chen <Stephen.Chen@atheros.com>
Subject: Re: Generic events for wake up from S1-S4
Date: Thu, 23 Jul 2009 16:31:27 -0400 [thread overview]
Message-ID: <8233.1248381087@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 23 Jul 2009 21:51:14 +0200." <20090723195114.GR28158@elf.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On Thu, 23 Jul 2009 21:51:14 +0200, Pavel Machek said:
> Ok, but then we should not be talking about wake up events,
> but... events.
>
> Like "lid opened", "wake packet came", ... . And deliver them even
> when they happen during run-time. That's okay with me.
That's actually a sane thing to do - for instance, one of the main uses
of "wake on LAN" in many environments is to wake up a box to do software
upgrades. And if we're already up-and-running, and we "know" (from site
policy) that a W-o-L packet is only sent because IT is pushing updates,
it may make a lot of sense to catch a "wake packet" event, and go ahead
and start the software updater *anyhow* (with suitable notification/confirm
dialog to the poor guy still working on that presentation at 2AM, of course :)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2009-07-23 20:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 22:11 Generic events for wake up from S1-S4 Luis R. Rodriguez
2009-07-14 23:53 ` Pavel Machek
2009-07-15 15:51 ` Luis R. Rodriguez
2009-07-15 15:56 ` Luis R. Rodriguez
2009-07-15 18:00 ` Luis R. Rodriguez
2009-07-18 10:37 ` Pavel Machek
2009-07-18 20:02 ` Luis R. Rodriguez
2009-07-18 23:56 ` Henrique de Moraes Holschuh
2009-07-20 16:27 ` Luis R. Rodriguez
2009-07-21 15:10 ` Henrique de Moraes Holschuh
2009-07-23 14:57 ` Pavel Machek
2009-07-23 18:57 ` Henrique de Moraes Holschuh
2009-07-23 19:13 ` Pavel Machek
2009-07-23 19:45 ` Henrique de Moraes Holschuh
2009-07-23 19:51 ` Pavel Machek
2009-07-23 20:10 ` Henrique de Moraes Holschuh
2009-07-23 21:27 ` Rafael J. Wysocki
2009-07-24 0:53 ` ykzhao
2009-07-24 13:39 ` Henrique de Moraes Holschuh
2009-07-24 14:49 ` Johannes Berg
2009-07-24 15:25 ` Luis R. Rodriguez
2009-07-23 20:31 ` Valdis.Kletnieks [this message]
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=8233.1248381087@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Stephen.Chen@atheros.com \
--cc=hmh@hmh.eng.br \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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