From: Hans Verkuil <hverkuil@xs4all.nl>
To: Dean Anderson <linux-dev@sensoray.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] s2255drv: file handle cleanup
Date: Wed, 05 Feb 2014 08:10:20 +0100 [thread overview]
Message-ID: <52F1E3DC.30507@xs4all.nl> (raw)
In-Reply-To: <1391553393-17672-1-git-send-email-linux-dev@sensoray.com>
On 02/04/2014 11:36 PM, Dean Anderson wrote:
> Removes most parameters from s2255_fh. These elements belong in s2255_ch.
> In the future, s2255_fh will be removed when videobuf2 is used. videobuf2
> has convenient and safe functions for locking streaming resources.
>
> The removal of s2255_fh (and s2255_fh->resources) was not done now to
> avoid using videobuf_queue_is_busy.
>
> videobuf_queue_is busy may be unsafe as noted by the following comment
> in videobuf-core.c:
> "/* Locking: Only usage in bttv unsafe find way to remove */"
>
> Signed-off-by: Dean Anderson <linux-dev@sensoray.com>
> ---
> drivers/media/usb/s2255/s2255drv.c | 224 +++++++++++++++++-------------------
> 1 file changed, 105 insertions(+), 119 deletions(-)
>
> diff --git a/drivers/media/usb/s2255/s2255drv.c b/drivers/media/usb/s2255/s2255drv.c
> index 2e24aee..3ea1bd5e 100644
> --- a/drivers/media/usb/s2255/s2255drv.c
> +++ b/drivers/media/usb/s2255/s2255drv.c
> @@ -251,6 +251,8 @@ struct s2255_vc {
> unsigned int height;
> const struct s2255_fmt *fmt;
> int idx; /* channel number on device, 0-3 */
> + struct videobuf_queue vb_vidq;
> + enum v4l2_buf_type type;
The whole type field can be dropped completely. This driver only support the
VIDEO_CAPTURE type anyway.
> };
Thank you for splitting up the large patch into smaller pieces. I plan to
review them Friday or Monday.
Regards,
Hans
prev parent reply other threads:[~2014-02-05 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:36 [PATCH] s2255drv: file handle cleanup Dean Anderson
2014-02-04 23:10 ` Dean Anderson
2014-02-05 7:16 ` Hans Verkuil
2014-02-05 7:10 ` Hans Verkuil [this message]
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=52F1E3DC.30507@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-dev@sensoray.com \
--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