On Mon, Feb 04, 2013 at 10:50:52AM +0000, Russell King - ARM Linux wrote: > On Mon, Feb 04, 2013 at 03:02:49AM +0100, Markus F.X.J. Oberhumer wrote: > > At least akpm did approve the LZO update for inclusion into 3.7, but the code > > still has not been merged into the main tree. > > > On 2012-10-09 21:26, Andrew Morton wrote: > > > [...] > > > The changes look OK to me. Please ask Stephen to include the tree in > > > linux-next, for a 3.7 merge. > > > > Well, this probably means I have done a rather poor marketing. > > I assume this code is sitting in *your* tree? How do you think it gets > into mainline? > > There is no automatic way that code from linux-next gets merged into > mainline. That is up to the tree owner to make happen, either by getting > their tree into a parent maintainers tree, or if there is none, asking > Linus to pull your tree at the appropriate time. My feeling is that in this case it is unneccessarily hard for an outside contributor to get a patch accepted, all because get_maintainer.pl doesn't put someone in charge. Apparently it doesn't work to put all the usual maintainer responsibilities onto the shoulders of a Linux development novice. Thus it would be nice if some maintainer would come forward and offer to handle the patches for Markus. Thanks, Johannes -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
