Em 03-01-2011 14:48, Sylwester Nawrocki escreveu:
> Hi Mauro,

> Marek Szyprowski (4):
>       v4l: mem2mem: port to videobuf2

This one didn't compile:

drivers/media/video/mem2mem_testdev.c: In function ‘device_process’:
drivers/media/video/mem2mem_testdev.c:232: warning: assignment from 
incompatible pointer type
drivers/media/video/mem2mem_testdev.c:233: warning: assignment from 
incompatible pointer type
drivers/media/video/mem2mem_testdev.c: In function ‘vidioc_g_fmt’:
drivers/media/video/mem2mem_testdev.c:429: warning: assignment from 
incompatible pointer type
drivers/media/video/mem2mem_testdev.c: In function ‘vidioc_s_fmt’:
drivers/media/video/mem2mem_testdev.c:528: warning: assignment from 
incompatible pointer type
drivers/media/video/mem2mem_testdev.c: In function ‘m2mtest_buf_queue’:
drivers/media/video/mem2mem_testdev.c:828: warning: passing argument 2 of 
‘v4l2_m2m_buf_queue’ from incompatible pointer type
include/media/v4l2-mem2mem.h:134: note: expected ‘struct vb2_buffer *’ but 
argument is of type ‘struct videobuf_queue *’
drivers/media/video/mem2mem_testdev.c:828: error: too many arguments to 
function ‘v4l2_m2m_buf_queue’
drivers/media/video/mem2mem_testdev.c: In function ‘m2mtest_open’:
drivers/media/video/mem2mem_testdev.c:869: warning: passing argument 1 of 
‘v4l2_m2m_ctx_init’ from incompatible pointer type
include/media/v4l2-mem2mem.h:128: note: expected ‘struct v4l2_m2m_dev *’ but 
argument is of type ‘struct m2mtest_ctx *’
drivers/media/video/mem2mem_testdev.c:869: warning: passing argument 3 of 
‘v4l2_m2m_ctx_init’ from incompatible pointer type
include/media/v4l2-mem2mem.h:128: note: expected ‘int (*)(void *, struct 
vb2_queue *, struct vb2_queue *)’ but argument is of type ‘void (*)(void *, 
struct videobuf_queue *, enum v4l2_buf_type)’

I'm removing it from my queue. Please, resend it with the fixes against my 
experimental tree.

Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to