All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL for 3.8-final] media-fixes
Date: Mon, 03 Dec 2012 12:32:11 -0200	[thread overview]
Message-ID: <50BCB7EB.6090707@redhat.com> (raw)

Hi Linus,

Please pull from:
   git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media v4l_for_linus

For some driver fixes for s5p/exynos (mostly race fixes).

Thanks!
Mauro

-

The following changes since commit 86163adb8125a4ce85e0b23a50be82bd8c0daf95:

   [media] rtl28xxu: 0ccd:00d7 TerraTec Cinergy T Stick+ (2012-11-22 12:04:53 -0200)

are available in the git repository at:

   git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media v4l_for_linus

for you to fetch changes up to d2a0db1ee01aea154ccc460e45a16857e32c4427:

   [media] s5p-mfc: Handle multi-frame input buffer (2012-11-26 18:43:27 -0200)

----------------------------------------------------------------
Arun Kumar K (2):
       [media] s5p-mfc: Bug fix of timestamp/timecode copy mechanism
       [media] s5p-mfc: Handle multi-frame input buffer

Shaik Ameer Basha (1):
       [media] exynos-gsc: Fix settings for input and output image RGB type

Sylwester Nawrocki (5):
       [media] s5p-fimc: Prevent race conditions during subdevs registration
       [media] s5p-fimc: Don't use mutex_lock_interruptible() in device release()
       [media] fimc-lite: Don't use mutex_lock_interruptible() in device release()
       [media] exynos-gsc: Don't use mutex_lock_interruptible() in device release()
       [media] exynos-gsc: Add missing video device vfl_dir flag initialization

  drivers/media/platform/exynos-gsc/gsc-m2m.c     |  4 ++--
  drivers/media/platform/exynos-gsc/gsc-regs.h    | 16 ++++++++--------
  drivers/media/platform/s5p-fimc/fimc-capture.c  | 10 +++++++---
  drivers/media/platform/s5p-fimc/fimc-lite.c     |  6 ++++--
  drivers/media/platform/s5p-fimc/fimc-m2m.c      |  3 +--
  drivers/media/platform/s5p-fimc/fimc-mdevice.c  |  4 ++--
  drivers/media/platform/s5p-mfc/s5p_mfc.c        |  7 ++-----
  drivers/media/platform/s5p-mfc/s5p_mfc_opr_v6.c |  2 +-
  8 files changed, 27 insertions(+), 25 deletions(-)


                 reply	other threads:[~2012-12-03 14:32 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=50BCB7EB.6090707@redhat.com \
    --to=mchehab@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.