From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: linux-media@vger.kernel.org
Cc: open list <linux-kernel@vger.kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
paul.kocialkowski@bootlin.com, ezequiel@collabora.com,
treding@nvidia.com, niklas.soderlund+renesas@ragnatech.se,
sakari.ailus@linux.intel.com,
Hans Verkuil <hans.verkuil@cisco.com>,
mchehab@kernel.org, lkft-triage@lists.linaro.org,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: test VIDIOC_G/S_PARM: FAIL on stable 4.14, 4.9 and 4.4
Date: Mon, 13 May 2019 19:02:26 +0530 [thread overview]
Message-ID: <CA+G9fYuC8dgKs04HmyCaKeQ_xwqKBxnh=zsOFjQK+3Fq7AZRyw@mail.gmail.com> (raw)
Do you see test VIDIOC_G/S_PARM: FAIL on stable 4.14, 4.9 and 4.4
kernel branches ?
test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
fail: ../../../v4l-utils-1.16.0/utils/v4l2-compliance/v4l2-test-formats.cpp(1132):
reserved not zeroed
test VIDIOC_G/S_PARM: FAIL
Test passes on mainline, -next, 5.0 and 4.19
Test failed on 4.14, 4.9 and 4.4
steps to reproduce:
# boot any 4.9/4.14 kernel on x86_64 / Juno / hikey device
# install v4l-utils package
# modprobe vivid.ko no_error_inj=1
# v4l2-compliance -v -d /dev/video0
Full test log,
https://lkft.validation.linaro.org/scheduler/job/708755#L1791
Test results comparison on all branches,
https://qa-reports.linaro.org/_/comparetest/?project=22&project=6&project=58&project=135&project=40&project=23&project=159&suite=v4l2-compliance&test=VIDIOC_G-S_PARM
Best Regards
Naresh Kamboju
next reply other threads:[~2019-05-13 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 13:32 Naresh Kamboju [this message]
2019-05-13 13:38 ` test VIDIOC_G/S_PARM: FAIL on stable 4.14, 4.9 and 4.4 Hans Verkuil
2019-05-20 13:56 ` Naresh Kamboju
2019-05-28 10:16 ` Naresh Kamboju
2019-05-28 11:57 ` Hans Verkuil
2019-05-28 12:23 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+G9fYuC8dgKs04HmyCaKeQ_xwqKBxnh=zsOFjQK+3Fq7AZRyw@mail.gmail.com' \
--to=naresh.kamboju@linaro.org \
--cc=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=paul.kocialkowski@bootlin.com \
--cc=sakari.ailus@linux.intel.com \
--cc=samitolvanen@google.com \
--cc=treding@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).