> my only concern being: > http://wiki.meego.com/MeeGo_kernel_documentation_for_contributors - quote: > "The MeeGo project really wants Device drivers and other kernel code to > be developed for, and integrated in, the kernel.org kernel as maintained > by Linus Torvalds. Every patch we carry has a cost for us, and we do not > want to carry long term patches. > > So if you want to develop a device driver for MeeGo, please develop your > driver for, and submit your driver to, the kernel.org Linux kernel. In > fact, this is a requirement for MeeGo! " > > It is a good approach - we dont take patches to MeeGo kernel which are > not posted upstream, aka if there are review comments there, we'd have > to fix them anyways - as they are relevant to us in MeeGo as well, in > effect it implies that a patch would be in some shape upstream-able > before getting into MeeGo kernel - much larger review base, much better > quality, albiet a bit slower.. > > Relevance of my above rambling is this: patch2&3 is not posted upstream, > and not got real quality reviews - may not be good for us in MeeGo perhaps? In fact, patch 2 I submitted to meego-kernel was also included in the patch I send to linux-mmc mail list. Only patch3 was missed.
Regards Chuanxiao _______________________________________________ Meego-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
