public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Alexey Starikovskiy <aystarik@gmail.com>,
	linux-pm@lists.linux-foundation.org,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Nigel Cunningham <nigel@nigel.suspend2.net>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: ACPI code in platform mode hibernation code paths (was: Re: [PATCH] swsusp: do not use pm_ops)
Date: Fri, 04 May 2007 12:54:32 +0200	[thread overview]
Message-ID: <1178276072.7408.7.camel@johannes.berg> (raw)
In-Reply-To: <20070503224807.GD13426@elf.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

On Fri, 2007-05-04 at 00:48 +0200, Pavel Machek wrote:

> Crazy idea... could we kill hibernate_ops-like struct, and just create
> a device for ACPI, using its suspend()/resume()/whatever callbacks to
> do the ACPI magic?

Doesn't that have the ordering problem again? You must ensure that this
sysdev is suspended as the last one, and that's currently impossible if
ACPI is modular.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  parent reply	other threads:[~2007-05-04 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070425072350.GA6866@ucw.cz>
     [not found] ` <200705021542.24988.rjw@sisk.pl>
     [not found]   ` <8f8ff01d0705020711r630b8b92sdd2cd9316eb39edc@mail.gmail.com>
2007-05-02 19:26     ` ACPI code in platform mode hibernation code paths (was: Re: [PATCH] swsusp: do not use pm_ops) Rafael J. Wysocki
2007-05-03 22:48       ` Pavel Machek
2007-05-03 23:14         ` Rafael J. Wysocki
2007-05-04 10:54         ` Johannes Berg [this message]
2007-05-04 12:08           ` Pavel Machek
2007-05-04 12:29             ` 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=1178276072.7408.7.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=aystarik@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=penberg@cs.helsinki.fi \
    --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