> IMHO the suspend code is currently way too much of a moving target which > results in this mess. > > The correct order seems to be: 0. Get someone to sign up as a maintainer for suspend, so we have someone to blame for the mess? :-) > 1. agree on what the suspend code as a whole should look like > 2. implement this > 3. fix ALL drivers to work at least as good as they do today > 4. get it tested in -mm > 5. fix all bugs people run into > 6. submit it for inclusion in Linus' tree > 7. quickly work on the most likely big amount of bug reports > > Step 1 is the most important one - evolving code is often something > good, but in this case with different people trying to evolve the > suspend code in different directions it simply results in a big mess. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
