Hi! > >> Question though -- has every feature ever added to the kernel been a > >> feature that there's pre-existing usage of? Seems like a chicken and > >> egg problem. Also, some people seem to think there's value in being > >> able to build kernels "out of the box" that work with the Android > >> userspace -- given that there are a few devices out there that have > >> that userspace on 'em. > > > > We generally try to merge new features like this along with code that > > uses said feature, but there are always exceptions. We've merged code > > one release or more before the new code gets used for example, which is > > fine IMO. What we don't want to see is some new drop of code added and > > abandoned, but you already knew that. > > If Android guys provided a bare minimal Debian system with suspend > blockers that people can take a look at and try, I think that would be > a good proof of concept. And a bare minimum to get the patches merged. Yes, that would certainly help. I guess this is the major point -- as suspend blockers seem very suitable for android, they don't seem suitable for anyone else... -- (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
