Re: -mm swsusp: do not default to platform/firmware
From: Nigel Cunningham (ncunningham_at_linuxmail.org)
Date: 07/29/04
- Previous message: Giuliano Pochini: "Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c"
- In reply to: Pavel Machek: "Re: -mm swsusp: do not default to platform/firmware"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Pavel Machek <pavel@ucw.cz> Date: Thu, 29 Jul 2004 18:03:48 +1000
Hi.
On Thu, 2004-07-29 at 17:38, Pavel Machek wrote:
> Threads that are "NOFREEZE" should be carefull not to do anything bad
> to drivers, and if it works as NOFREEZE for swsusp, it will work in
> S3, too. No need to do additional work of freezing based on new state.
Yes. It helps to remember that even if they're NOFREEZE, they'll still
be affected by the driver suspending and resuming that's done in both S3
(I assume) and S4 support.
Regards,
Nigel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Giuliano Pochini: "Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c"
- In reply to: Pavel Machek: "Re: -mm swsusp: do not default to platform/firmware"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
