From: Johannes Berg <johannes@sipsolutions.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: ykzhao <yakui.zhao@intel.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Pavel Machek <pavel@ucw.cz>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>,
Jouni Malinen <j@w1.fi>,
linux-wireless <linux-wireless@vger.kernel.org>,
Stephen Chen <Stephen.Chen@atheros.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: Generic events for wake up from S1-S4
Date: Fri, 24 Jul 2009 16:49:16 +0200 [thread overview]
Message-ID: <1248446956.32151.0.camel@johannes.local> (raw)
In-Reply-To: <20090724133903.GA18827@khazad-dum.debian.net>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
On Fri, 2009-07-24 at 10:39 -0300, Henrique de Moraes Holschuh wrote:
> ACPI notifications are hard to extend, I think. Please correct me if I am
> wrong.
ACPI is the wrong place anyway, since it's fundamentally platform
dependent. Unlike the rest of suspend and wake functionality.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-24 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43e72e890907150851m69cd2de6lfb71596fbfac30e6@mail.gmail.com>
[not found] ` <20090723195114.GR28158@elf.ucw.cz>
[not found] ` <20090723201050.GD19369@khazad-dum.debian.net>
2009-07-23 21:27 ` Generic events for wake up from S1-S4 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 [this message]
2009-07-24 15:25 ` Luis R. Rodriguez
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=1248446956.32151.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Stephen.Chen@atheros.com \
--cc=hmh@hmh.eng.br \
--cc=j@w1.fi \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=yakui.zhao@intel.com \
/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