diff options
| author | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2018-09-14 05:46:29 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-11-21 11:27:36 +0300 |
| commit | 1fe3db85c38007c48200d1b100ee16652de0c12e (patch) | |
| tree | b3cf263669f897835c5df43eafa201294756db8e /fs | |
| parent | 77a61c5a570551be9698f7b8deb212fa9c9fd135 (diff) | |
| download | linux-1fe3db85c38007c48200d1b100ee16652de0c12e.tar.xz | |
media: em28xx: make v4l2-compliance happier by starting sequence on zero
commit afeaade90db4c5dab93f326d9582be1d5954a198 upstream.
The v4l2-compliance tool complains if a video doesn't start
with a zero sequence number.
While this shouldn't cause any real problem for apps, let's
make it happier, in order to better check the v4l2-compliance
differences before and after patchsets.
This is actually an old issue. It is there since at least its
videobuf2 conversion, e. g. changeset 3829fadc461 ("[media]
em28xx: convert to videobuf2"), if VB1 wouldn't suffer from
the same issue.
Cc: stable@vger.kernel.org
Fixes: d3829fadc461 ("[media] em28xx: convert to videobuf2")
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions