From: Nigel Cunningham <ncunningham@cyclades.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
Pavel Machek <pavel@ucw.cz>, Meelis Roos <mroos@linux.ee>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: reboot vs poweroff
Date: Fri, 02 Sep 2005 07:11:40 +1000 [thread overview]
Message-ID: <1125609100.4785.30.camel@localhost> (raw)
In-Reply-To: <m164tkpryx.fsf@ebiederm.dsl.xmission.com>
Hi.
On Fri, 2005-09-02 at 04:23, Eric W. Biederman wrote:
> Pierre Ossman <drzeus-list@drzeus.cx> writes:
> >
> > Patch tested and works fine here. You should probably make a note in the
> > bugzilla so we don't get a conflicting merge from the ACPI folks.
>
> Thanks.
>
> If I can figure out bugzilla...
>
> > I suppose Nigel should use this function in swsusp2 aswell?
All I did was start calling pm_ops->prepare, ->enter and ->finish
regardless of the powerdown method, instead of only for S3 or S4. It
seems to be working fine. If, however, we should be doing things
differently, I'm happy to comply. What's the authoritative word?
Regards,
Nigel
> If he is doing the same thing yes.
>
> Eric
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
next prev parent reply other threads:[~2005-09-01 21:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 0:17 Linux 2.6.13 Linus Torvalds
2005-08-29 0:43 ` Jesper Juhl
2005-08-29 3:05 ` Linus Torvalds
2005-08-29 10:57 ` Steven Rostedt
2005-08-29 12:17 ` Nigel Cunningham
2005-08-29 12:25 ` Jörn Engel
2005-08-29 12:28 ` Nigel Cunningham
2005-08-29 14:25 ` Antonino A. Daplas
2005-08-29 14:42 ` Steven Rostedt
2005-08-29 14:50 ` Linus Torvalds
2005-08-29 15:44 ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes Steven Rostedt
2005-08-29 18:04 ` [PATCH] convert signal handling of NODEFER to act like other Unix boxes. [take2] Steven Rostedt
2005-08-29 12:19 ` Linux 2.6.13 Nigel Cunningham
2005-08-29 14:22 ` Roland Dreier
2005-09-01 6:24 ` reboot vs poweroff (was: Linux 2.6.13) Meelis Roos
2005-09-01 6:48 ` Nigel Cunningham
2005-09-01 7:33 ` Meelis Roos
2005-09-01 12:32 ` Pierre Ossman
2005-09-01 12:48 ` Nigel Cunningham
2005-09-01 15:15 ` Eric W. Biederman
2005-09-01 15:19 ` reboot vs poweroff Pierre Ossman
2005-09-01 17:00 ` Eric W. Biederman
2005-09-01 18:19 ` Pierre Ossman
2005-09-01 18:23 ` Eric W. Biederman
2005-09-01 21:11 ` Nigel Cunningham [this message]
2005-09-02 4:46 ` Eric W. Biederman
2005-09-01 20:22 ` Pavel Machek
2005-09-02 4:26 ` Eric W. Biederman
2005-09-01 21:09 ` reboot vs poweroff (was: Linux 2.6.13) Nigel Cunningham
2005-08-29 18:23 ` Oops in 2.6.13 (was Linux 2.6.13 ) Masoud Sharbiani
2005-08-29 20:13 ` Lee Revell
2005-08-30 3:47 ` Masoud Sharbiani
2005-08-30 22:41 ` Linux 2.6.13 Henrik Persson
2005-09-01 2:29 ` Greg KH
2005-09-03 9:22 ` Henrik Persson
2005-08-31 12:42 ` Alexandre Buisse
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 18:23 reboot vs poweroff Brown, Len
2005-09-02 4:43 ` Eric W. Biederman
2005-09-10 21:07 ` Eric W. Biederman
2005-09-11 8:43 ` Meelis Roos
2005-09-11 8:53 ` 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=1125609100.4785.30.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=drzeus-list@drzeus.cx \
--cc=ebiederm@xmission.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=pavel@ucw.cz \
/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