Hi!And what do you expect? We have three people working on hibernation, and suspend-to-ram was created as "oh, if we do this, this, and this, we get get suspend-to-ram with existing code". You'd be seriously overstaffed in FPU side, and seriously understaffed on ALU side. This is basically what happened here. I tell people to get hibernation to work _first_ because it is usually easier. And what does that mean? We need three people to work on suspend-to-RAM. Heck, we need at least _one_ person to work on suspend-to-RAM, but he needs to be listed in MAINTAINERS. With hibernation people trying to maintain suspend in their spare cycles, how do you expect suspend to work? Similar to hibernation, that's how it looks today. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Herbert Xu | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Rémi Denis-Courmont | [PATCH 01/14] Phonet global definitions |
