From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Boris Brezillon <boris.brezillon@collabora.com>,
Eric Anholt <eric@anholt.net>
Subject: Re: [PATCH 6/7] vc04_services/bcm2835-camera: set device_caps in struct video_device
Date: Tue, 4 Jun 2019 13:30:48 +0200 [thread overview]
Message-ID: <20190604113048.GA18535@kroah.com> (raw)
In-Reply-To: <20190604111958.22331-7-hverkuil-cisco@xs4all.nl>
On Tue, Jun 04, 2019 at 01:19:57PM +0200, Hans Verkuil wrote:
> Instead of filling in the struct v4l2_capability device_caps
> field, fill in the struct video_device device_caps field.
>
> That way the V4L2 core knows what the capabilities of the
> video device are.
>
> But this only really works if all drivers use this, so convert
> this driver accordingly.
>
> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Eric Anholt <eric@anholt.net>
> ---
> .../staging/vc04_services/bcm2835-camera/bcm2835-camera.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-06-04 11:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 11:19 [PATCH 0/7] media: set device_caps in struct video_device Hans Verkuil
2019-06-04 11:19 ` [PATCH 1/7] media/radio: " Hans Verkuil
2019-06-04 11:19 ` [PATCH 2/7] media/usb: " Hans Verkuil
2019-06-04 11:19 ` [PATCH 3/7] rtl2832_sdr: " Hans Verkuil
2019-06-04 11:19 ` [PATCH 4/7] usb/gadget/f_uvc: " Hans Verkuil
2019-06-04 12:30 ` Laurent Pinchart
2019-06-04 12:49 ` Felipe Balbi
2019-06-04 11:19 ` [PATCH 5/7] touchscreen/sur40: " Hans Verkuil
2019-06-04 11:19 ` [PATCH 6/7] vc04_services/bcm2835-camera: " Hans Verkuil
2019-06-04 11:30 ` Greg Kroah-Hartman [this message]
2019-06-04 12:36 ` [PATCH 5/7 RESEND] touchscreen/sur40: " Hans Verkuil
2019-06-04 16:06 ` Dmitry Torokhov
2019-06-12 8:46 ` Florian Echtler
2019-06-12 7:19 ` Hans Verkuil
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=20190604113048.GA18535@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=boris.brezillon@collabora.com \
--cc=eric@anholt.net \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.