From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io
Cc: ezequiel Garcia <ezequiel@collabora.com>,
Gustavo Padovan <gustavo.padovan@collabora.com>,
anders.roxell@linaro.org
Subject: Re: [kernelci] media subsystem test pilot
Date: Wed, 12 Sep 2018 11:34:27 +0100 [thread overview]
Message-ID: <20180912103427.GD6062@sirena.org.uk> (raw)
In-Reply-To: <d0113fd0-801a-feff-af96-12a71ca27dc7@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On Wed, Sep 12, 2018 at 09:13:23AM +0100, Guillaume Tucker wrote:
> * add config fragment (similar to the kselftest one) with virtual
> video drivers enabled to test v4l2 framework on QEMU and get
> reference test results
Semi-orthogonal (and definitely not a blocker) but Anders Roxell (CCed)
was looking at proposing a config fragment for inclusion upstream which
would enable all the config options that add ABIs, mainly for use with
testsuites. The idea was that with such a fragment enabled there'd be a
good chance that any random testsuite would have what it needs from the
kernel without needing to maintain lots of testsuite specific fragments,
especially if the config options change with kernel versions. I wonder
if it's also a good idea to have a fragment which enables all test/virtual
drivers for similar reasons.
> Does this sound like a good plan? If so, it would be good to start
> working on it next week if we want to get something done in time for
> ELCE and give a chance to developers to provide some feedback on the
> test results.
Makes sense to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-09-12 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 8:13 media subsystem test pilot Guillaume Tucker
2018-09-12 8:51 ` [kernelci] " Milosz Wasilewski
2018-09-12 15:55 ` Ezequiel Garcia
2018-09-12 10:34 ` Mark Brown [this message]
2018-09-12 20:15 ` Kevin Hilman
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=20180912103427.GD6062@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=ezequiel@collabora.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci@groups.io \
/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