On Mon, May 11, 2009 at 11:13 AM, Yi Sun <[email protected]> wrote: > On Mon, 2009-05-11 at 11:04 -0700, Greg KH wrote: >> > I don't like such a reason. If 2.6.27 is an obsolete branch, it is >> > fair to reject by this reason. >> > But 2.6.27 is still the master branch (correct if I'm wrong), >> > I can't see any rationality to reject or ignore an enhancement or a >> > bugfix. >> >> Why would you need these patches accepted into the .27 tree? For new >> android devices, aren't you using .29 already? Why would you want to >> use .27 instead? >> >> confused as to why exactly you need these patches in the tree, >> > No, Android is not using .29 yet. The CUPCAKE is still using .27. As > matter fact for x86 platforms, the .29 does not work yet.
Is is kernel problems that are keeping .29 from working properly? From what I have seen, it is just a matter of syncing up the repositories, not any basic technical reason for not moving forward yet. Or am I mistaken? Are there bugs reported somewhere against .29 that are yet to be resolved that is keeping it back? thanks, greg k-h --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
