All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [GIT PULL FOR v3.14] Three fixes
Date: Mon, 10 Mar 2014 13:45:19 +0100	[thread overview]
Message-ID: <531DB3DF.6000301@xs4all.nl> (raw)

Three small fixes for 3.14:

- while working on the EDID changes Laurent discovered that the ioctl numbers
  specified in v4l2-compat-ioctl32 were wrong and have been from the beginning.
  Fix that. NOTE: this patch was also included with the 3.15 EDID pull request
  I posted today.

- The v4l2-dv-timings module was missing the module name, description and license.
  Because of the missing license any driver that loads that module will taint the
  kernel. Definitely not what I intended.

- Fix a saa7134 suspend bug: https://bugzilla.kernel.org/show_bug.cgi?id=69581

Regards,

	Hans

The following changes since commit bfd0306462fdbc5e0a8c6999aef9dde0f9745399:

  [media] v4l: Document timestamp buffer flag behaviour (2014-03-05 16:48:28 -0300)

are available in the git repository at:

  git://linuxtv.org/hverkuil/media_tree.git for-v3.14f

for you to fetch changes up to b500d6a1664622cb7ba6ad27a1bc2bbce1022587:

  saa7134: fix WARN_ON during resume. (2014-03-07 12:11:19 +0100)

----------------------------------------------------------------
Hans Verkuil (3):
      v4l2-compat-ioctl32: fix wrong VIDIOC_SUBDEV_G/S_EDID32 support.
      v4l2-dv-timings: add module name, description, license.
      saa7134: fix WARN_ON during resume.

 drivers/media/pci/saa7134/saa7134-cards.c     | 4 ++--
 drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 4 ++--
 drivers/media/v4l2-core/v4l2-dv-timings.c     | 4 ++++
 3 files changed, 8 insertions(+), 4 deletions(-)

                 reply	other threads:[~2014-03-10 12:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=531DB3DF.6000301@xs4all.nl \
    --to=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 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.