From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
barryn-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org,
marado-oe7qfRrRQfcmha6Ds7sm0l6hYfS7NtTn@public.gmane.org,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: 2.6.11-rc4-mm1: something is wrong with swsusp powerdown
Date: 01 Mar 2005 04:12:50 -0700 [thread overview]
Message-ID: <m1psyjr559.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050301105448.GG1345-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org> writes:
> Yes, the patch is very ugly. If something like this needs to be done,
> then perhaps acpi should properly register into driver model and do
> the work there. This will also mean code will be called consistently.
I totally agree. Do you have an example of how a non-device
can do this?
In particular something that gets as close to shutting down
the system devices as possible. But gets called before that.
Or perhaps acpi should simply be setup to be the first system device?
Eric
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-01 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050228231721.GA1326@elf.ucw.cz>
[not found] ` <20050228231721.GA1326-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-01 9:52 ` 2.6.11-rc4-mm1: something is wrong with swsusp powerdown Andrew Morton
2005-03-01 10:54 ` Pavel Machek
[not found] ` <20050301105448.GG1345-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-01 11:12 ` Eric W. Biederman [this message]
2005-03-01 12:02 ` Pavel Machek
2005-03-01 11:08 ` Eric W. Biederman
2005-03-01 12:08 ` Pavel Machek
2005-03-01 17:33 ` Eric W. Biederman
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=m1psyjr559.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=barryn-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marado-oe7qfRrRQfcmha6Ds7sm0l6hYfS7NtTn@public.gmane.org \
--cc=pavel-AlSwsSmVLrQ@public.gmane.org \
/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