linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antonio Ospite <ao2@ao2.it>
To: Linux Media <linux-media@vger.kernel.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Hans Verkuil <hverkuil@xs4all.nl>, Antonio Ospite <ao2@ao2.it>
Subject: [PATCH 0/7] gspca: pass all v4l2-compliance tests + minor fixes
Date: Wed,  9 Mar 2016 17:03:14 +0100	[thread overview]
Message-ID: <1457539401-11515-1-git-send-email-ao2@ao2.it> (raw)

Hi,

after applying this patchset gspca passes all v4l2-compliance tests, at
least it does with a PS3 Eye.

 - Patch 1 removes some magic numbers in subdrivers.
 - Patch 2 is a correctness fix, but it does not bring any functional
   changes.
 - Patch 3 is a readability improvement by itself, but it's also
   a preliminary change for patch 4.
 - Patches from 4 to 7 are the actual compliance fixes.

More details are in the commit messages.

Thanks,
   Antonio

Antonio Ospite (7):
  [media] gspca: ov534/topro: use a define for the default framerate
  [media] gspca: fix setting frame interval type in
    vidioc_enum_frameintervals()
  [media] gspca: rename wxh_to_mode() to wxh_to_nearest_mode()
  [media] gspca: fix a v4l2-compliance failure about
    VIDIOC_ENUM_FRAMEINTERVALS
  [media] gspca: fix a v4l2-compliance failure about buffer timestamp
  [media] gspca: fix a v4l2-compliance failure during VIDIOC_REQBUFS
  [media] gspca: fix a v4l2-compliance failure during read()

 drivers/media/usb/gspca/gspca.c | 36 +++++++++++++++++++++++-------------
 drivers/media/usb/gspca/ov534.c |  7 +++----
 drivers/media/usb/gspca/topro.c |  6 ++++--
 3 files changed, 30 insertions(+), 19 deletions(-)

-- 
Antonio Ospite
http://ao2.it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

             reply	other threads:[~2016-03-09 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 16:03 Antonio Ospite [this message]
2016-03-09 16:03 ` [PATCH 1/7] [media] gspca: ov534/topro: use a define for the default framerate Antonio Ospite
2016-03-09 16:03 ` [PATCH 2/7] [media] gspca: fix setting frame interval type in vidioc_enum_frameintervals() Antonio Ospite
2016-03-09 16:03 ` [PATCH 3/7] [media] gspca: rename wxh_to_mode() to wxh_to_nearest_mode() Antonio Ospite
2016-03-09 16:03 ` [PATCH 4/7] [media] gspca: fix a v4l2-compliance failure about VIDIOC_ENUM_FRAMEINTERVALS Antonio Ospite
2016-03-09 16:03 ` [PATCH 5/7] [media] gspca: fix a v4l2-compliance failure about buffer timestamp Antonio Ospite
2016-03-09 16:03 ` [PATCH 6/7] [media] gspca: fix a v4l2-compliance failure during VIDIOC_REQBUFS Antonio Ospite
2016-03-09 16:10   ` Hans Verkuil
2016-03-10 14:54   ` Hans de Goede
2016-03-14 15:02     ` Antonio Ospite
2016-03-14 15:34       ` Hans de Goede
2016-03-09 16:03 ` [PATCH 7/7] [media] gspca: fix a v4l2-compliance failure during read() Antonio Ospite
2016-03-10 15:59   ` Hans de Goede
2016-03-14 15:11     ` Antonio Ospite

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=1457539401-11515-1-git-send-email-ao2@ao2.it \
    --to=ao2@ao2.it \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@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 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).