Frank Schaefer 24a6d8497f [media] em28xx: refactor get_next_buf() and use it for vbi data, too
get_next_buf() and vbi_get_next_buf() do exactly the same just with a
different dma queue and buffer. Saving the new buffer pointer back to the
device struct in em28xx_urb_data_copy() instead of doing this from inside
these functions makes it possible to get rid of one of them.
Also refactor the function parameters and return type:
- pass a pointer to struct em28xx as parameter (instead of obtaining the
  pointer from the dma queue pointer with the container_of macro) like we do
  it in all other functions
- instead of using a pointer-pointer, return the pointer to the new buffer
  as return value of the function

Signed-off-by: Frank Schäfer <fschaefer.oss@googlemail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
2012-12-22 20:48:57 -02:00
..
2012-11-22 09:14:54 -10:00
2012-10-15 14:45:51 -04:00
2012-11-23 14:32:55 +01:00
2012-12-03 10:53:25 -08:00
2012-09-26 22:28:21 -04:00
2012-12-02 16:24:31 -08:00
2012-10-10 20:15:24 +09:00
2012-10-17 15:53:03 -05:00
2012-10-09 16:11:46 +09:00
2012-10-10 20:15:24 +09:00
2012-11-16 14:33:04 -08:00
2012-10-28 11:13:54 -07:00
2012-11-22 09:14:54 -10:00
2012-11-23 12:01:02 -10:00
2012-10-01 12:09:59 -07:00
2012-11-20 18:52:01 -10:00
2012-10-01 18:46:13 -07:00
2012-10-16 18:07:12 -07:00