On Thu, Feb 05, 2015 at 05:25:42PM +0200, Tomi Valkeinen wrote: > Hi, > > On 05/02/15 17:20, Sudip Mukherjee wrote: > > Hi, > > I have noticed that we do not have anything called fbdev-next so patches to fbdev does not appear in linux-next, but instead waits for the merge window. That may be because you might not have enough time to maintain a separate tree or any other reason. > > Can i help in any way to have a fbdev-next tree? I can have a tree in my server, where i can apply the patches that you are queuing for the next merge window (usually you will send reply to the list that it is queued). And that tree can act as fbdev-next. > > > > This was just an idea, and but I am willing to help you in any way to have a fbdev-next. > > I have 'for-next' branch in my tree > git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux.git which gets > pulled into linux-next, and that's where I push fbdev patches. > The reason for my mail Stephen in his mail "linux-next: tidy up of trees" mentioned that fbdev is not getting updated. But now when I am checking i am seeing my fbdev patches in linux-next. I should have checked before sending you the mail. Sorry for the noise. Sudip > Tomi > > -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
