public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: LMML <linux-media@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [GIT PULL FOR v3.7-rc] Samsung SoC media driver fixes
Date: Thu, 22 Nov 2012 19:21:42 +0100	[thread overview]
Message-ID: <50AE6D36.1060805@samsung.com> (raw)
In-Reply-To: <50AE6BAC.1030208@samsung.com>

Hi Mauro,

this is what I've just sent (this time from the office my samsung.com account)
to linux-media@vger.kernel.org. And can't see it neither on the mailing list
nor at the patchwork.

Regards,
Sylwester

On 11/22/2012 07:15 PM, Sylwester Nawrocki wrote:
> Hi Mauro,
> 
> The following changes since commit 30677fd9ac7b9a06555318ec4f9a0db39804f9b2:
> 
>   s5p-fimc: Fix potential NULL pointer dereference (2012-11-22 10:15:40 +0100)
> 
> are available in the git repository at:
> 
>   git://git.infradead.org/users/kmpark/linux-samsung media_fixes_for_v3.7
> 
> for you to fetch changes up to 28f497f26c67ab734bdb923b457016122368f69a:
> 
>   s5p-mfc: Handle multi-frame input buffer (2012-11-22 15:13:53 +0100)
> 
> This is a bunch of quite important fixes for the Exynos SoC drivers,
> please apply for v3.7 if possible. This depends on my previous pull
> request (I've applied the patches you indicated you take for v3.7
> previously to the media_fixes_for_v3.7 branch as well).
> 
> ----------------------------------------------------------------
> Arun Kumar K (2):
>       s5p-mfc: Bug fix of timestamp/timecode copy mechanism
>       s5p-mfc: Handle multi-frame input buffer
> 
> Shaik Ameer Basha (1):
>       exynos-gsc: Fix settings for input and output image RGB type
> 
> Sylwester Nawrocki (5):
>       s5p-fimc: Prevent race conditions during subdevs registration
>       s5p-fimc: Don't use mutex_lock_interruptible() in device release()
>       fimc-lite: Don't use mutex_lock_interruptible() in device release()
>       exynos-gsc: Don't use mutex_lock_interruptible() in device release()
>       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(-)
> 
> ---
> 
> Regards,
> Sylwester

  reply	other threads:[~2012-11-22 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 18:15 [GIT PULL FOR v3.7-rc] Samsung SoC media driver fixes Sylwester Nawrocki
2012-11-22 18:21 ` Sylwester Nawrocki [this message]
2012-11-22 18:55   ` Laurent Pinchart
2012-11-22 20:58     ` Sylwester Nawrocki
2012-11-26 16:09 ` Sylwester Nawrocki

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=50AE6D36.1060805@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    /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