| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 4 Jul 2007 16:40:12 +0200 From: "Rafael J. Wysocki" <rjw@...k.pl> To: Theodore Tso <tytso@....edu> Cc: Paul Mackerras <paulus@...ba.org>, Matthew Garrett <mjg59@...f.ucam.org>, linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway On Wednesday, 4 July 2007 14:41, Theodore Tso wrote: > On Wed, Jul 04, 2007 at 01:25:55PM +0200, Rafael J. Wysocki wrote: > > > Don't know what exactly? > > > > How many drivers will be adversely affected by the $subject change. > > Ok, so how about a CONFIG option which removes the freezer, so we can > find out experimentally how many people without it? We can make it be > experimental at first, or (my preference) make it be the default > initially, and if people complain that their laptop's suspend feature > is broken, we can tell them how to turn back on the > CONFIG_FREEZER_DEPRECATED option. The freezer is generally still necessary for hibernation, so I won't call it "DEPRECATED'. Moreover, I'd prefer to make drivers use different callbacks for hibernation and suspend before we do that. Greetings, Rafael -- "Premature optimization is the root of all evil." - Donald Knuth - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists