Hi Mauro, On Thursday 22 September 2011 00:20:09 Mauro Carvalho Chehab wrote: > Em 21-09-2011 18:58, Laurent Pinchart escreveu: > >> Aug,19 2011: v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats > >> http://patchwork.linuxtv.org/patch/7630 > > > > This one has been superseeded. Speaking of this, the next version of the > > patch will be needed for an fbdev driver that should make it to v3.3. > > Should I push NV24 support through your tree for v3.2 to make sure > > compilation won't break during the v3.3 merge window ? > > The better is to submit both patches to the same tree, getting the > maintainer's ack from the other side. I'm ok with either direction. If you > opt to sent the patches via fbdev tree, send me the latest version of it > for me to review and ack. linux-media has already been CC'ed. "[PATCH v3 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats" http://patchwork.linuxtv.org/patch/306/ > >> Sep, 5 2011: BUG: unable to handle kernel paging request at 6b6b6bcb > >> (v4l2_device_d > >> http://patchwork.linuxtv.org/patch/7779 > > > > Superseeded as well. > > > >> Sep,12 2011: [GIT,PULL,FOR,v3.1] v4l and uvcvideo fixes > >> http://patchwork.linuxtv.org/patch/7835 > > > > Please pull that :-) It's for v3.1, there's not much time left. > > I will. Thank you. > >> == Patches waiting for Laurent Pinchart review == > > > > [snip] > > > >> Jul,12 2011: v4l: mem2mem: add wait_{prepare,finish} ops to m2m_testdev > >> http://patchwork.linuxtv.org/patch/7431 > > > > I don't think that one is for me. > > > >> Jul,10 2011: [3/3] Make use of 8-bit and 16-bit YCrCb media bus pixel > >> codes in adv7 > >> http://patchwork.linuxtv.org/patch/7425 > > > > I don't think this one is for me either. > > Hmm.. not sure why I put those two for you. Will fix that on my control > files. > > Thank you! You're welcome. Thank you for your work on this, and the speed at which you got it running. -- Regards, Laurent Pinchart -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
