linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jernej Škrabec" <jernej.skrabec@siol.net>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	Boris Brezillon <boris.brezillon@collabora.com>
Subject: Re: [PATCH 1/3] cedrus: fill in bus_info for media device
Date: Tue, 03 Sep 2019 17:39:34 +0200	[thread overview]
Message-ID: <4505141.GLqKN8naU8@jernej-laptop> (raw)
In-Reply-To: <20190830092624.18228-2-hverkuil-cisco@xs4all.nl>

Hi!

Dne petek, 30. avgust 2019 ob 11:26:22 CEST je Hans Verkuil napisal(a):
> Fixes this compliance warning:
> 
> $ v4l2-compliance -m0
> v4l2-compliance SHA: b514d615166bdc0901a4c71261b87db31e89f464, 32 bits
> 
> Compliance test for cedrus device /dev/media0:
> 
> Media Driver Info:
>         Driver name      : cedrus
>         Model            : cedrus
>         Serial           :
>         Bus info         :
>         Media version    : 5.3.0
>         Hardware revision: 0x00000000 (0)
>         Driver version   : 5.3.0
> 
> Required ioctls:
>                 warn: v4l2-test-media.cpp(51): empty bus_info
>         test MEDIA_IOC_DEVICE_INFO: OK
> 
> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> ---
>  drivers/staging/media/sunxi/cedrus/cedrus.c | 2 ++
>  1 file changed, 2 insertions(+)

Reviewed-by: Jernej Skrabec <jernej.skrabec@siol.net>

Best regards,
Jernej



  reply	other threads:[~2019-09-03 15:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  9:26 [PATCH 0/3] cedrus: v4l2-compliance fixes Hans Verkuil
2019-08-30  9:26 ` [PATCH 1/3] cedrus: fill in bus_info for media device Hans Verkuil
2019-09-03 15:39   ` Jernej Škrabec [this message]
2019-08-30  9:26 ` [PATCH 2/3] cedrus: choose default pixelformat in try_fmt Hans Verkuil
2019-09-03 15:40   ` Jernej Škrabec
2019-08-30  9:26 ` [PATCH 3/3] cedrus: fix various format-related compliance issues Hans Verkuil
2019-09-03 15:43   ` Jernej Škrabec

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=4505141.GLqKN8naU8@jernej-laptop \
    --to=jernej.skrabec@siol.net \
    --cc=boris.brezillon@collabora.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=paul.kocialkowski@bootlin.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).