Re: [RFC PATCH] em28xx: fix bytesperline calculation in TRY_FMT

2013-01-29 Thread Mauro Carvalho Chehab
Em Tue, 29 Jan 2013 19:21:50 +0100 Hans Verkuil escreveu: > On Tue January 29 2013 18:51:46 Frank Schäfer wrote: > > Am 29.01.2013 10:49, schrieb Hans Verkuil: > > > This was part of my original em28xx patch series. That particular patch > > > combined two things: this fix and the change where TR

Re: [RFC PATCH] em28xx: fix bytesperline calculation in TRY_FMT

2013-01-29 Thread Hans Verkuil
On Tue January 29 2013 18:51:46 Frank Schäfer wrote: > Am 29.01.2013 10:49, schrieb Hans Verkuil: > > This was part of my original em28xx patch series. That particular patch > > combined two things: this fix and the change where TRY_FMT would no > > longer return -EINVAL for unsupported pixelformat

Re: [RFC PATCH] em28xx: fix bytesperline calculation in TRY_FMT

2013-01-29 Thread Frank Schäfer
Am 29.01.2013 10:49, schrieb Hans Verkuil: > This was part of my original em28xx patch series. That particular patch > combined two things: this fix and the change where TRY_FMT would no > longer return -EINVAL for unsupported pixelformats. The latter change was > rejected (correctly), but we all f

Re: [RFC PATCH] em28xx: fix bytesperline calculation in TRY_FMT

2013-01-29 Thread Devin Heitmueller
On Tue, Jan 29, 2013 at 4:49 AM, Hans Verkuil wrote: > This was part of my original em28xx patch series. That particular patch > combined two things: this fix and the change where TRY_FMT would no > longer return -EINVAL for unsupported pixelformats. The latter change was > rejected (correctly), b

[RFC PATCH] em28xx: fix bytesperline calculation in TRY_FMT

2013-01-29 Thread Hans Verkuil
This was part of my original em28xx patch series. That particular patch combined two things: this fix and the change where TRY_FMT would no longer return -EINVAL for unsupported pixelformats. The latter change was rejected (correctly), but we all forgot about the second part of the patch which fixe