From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org,
Boris Brezillon <boris.brezillon@collabora.com>,
Florian Echtler <floe@butterbrot.org>,
linux-input <linux-input@vger.kernel.org>
Subject: Re: [PATCH 5/7 RESEND] touchscreen/sur40: set device_caps in struct video_device
Date: Tue, 4 Jun 2019 09:06:50 -0700 [thread overview]
Message-ID: <20190604160650.GA226219@dtor-ws> (raw)
In-Reply-To: <1e12bc3d-3cb3-1f3d-b3bc-b25e3bf95523@xs4all.nl>
Hi Hans,
On Tue, Jun 04, 2019 at 02:36:27PM +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 touchscreen driver accordingly.
>
> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> Cc: Florian Echtler <floe@butterbrot.org>
> ---
> Resend, adding Dmitry and linux-input to the CC list.
>
> Dmitry, if you want to take this through your tree, then that's OK by me.
>
> Alternatively, it can go through the media tree, but then I need your Ack.
I am fine with it going through media tree.
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-06-04 16:06 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
2019-06-04 12:36 ` [PATCH 5/7 RESEND] touchscreen/sur40: " Hans Verkuil
2019-06-04 16:06 ` Dmitry Torokhov [this message]
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=20190604160650.GA226219@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=floe@butterbrot.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=linux-input@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox