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@infradead.org>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL FOR 2.6.39] s5p-fimc driver and videobuf2 fixes
Date: Tue, 08 Mar 2011 17:36:31 +0100	[thread overview]
Message-ID: <4D765B0F.8090803@samsung.com> (raw)
In-Reply-To: <4D70C495.5000200@samsung.com>

Mauro,

please ignore the below pull request. I've found some issues in s5p-fimc
patches so I want to fix this and resent the pull request. 
My apologies for the hassle.

Regards,
Sylwester

On 03/04/2011 11:53 AM, Sylwester Nawrocki wrote:
> Hi Mauro,
> 
> please pull the following change set, it's a couple of s5p-fimc driver
> fixes and updates after conversion to videobuf2. There are also two small
> corrections for the videobuf2 and documentation for NV12MT format.
> 
> 
> The following changes since commit 548b491f5a3221e26c0b08dece18fdc62930fe5e:
> 
>   [media] media/radio/wl1273: fix build errors (2011-02-27 21:36:52 -0300)
> 
> are available in the git repository at:
>   git://git.infradead.org/users/kmpark/linux-2.6-samsung s5p_fimc_for_mauro
> 
> Andrzej Pietrasiewicz (1):
>       v4l2: vb2-dma-sg: fix memory leak
> 
> Kamil Debski (1):
>       v4l: Documentation for the NV12MT format
> 
> Marek Szyprowski (1):
>       v4l2: vb2: fix queue reallocation and REQBUFS(0) case
> 
> Sungchun Kang (1):
>       s5p-fimc: fix ISR and buffer handling for fimc-capture
> 
> Sylwester Nawrocki (6):
>       s5p-fimc: Prevent oops when i2c adapter is not available
>       s5p-fimc: Prevent hanging on device close and fix the locking
>       s5p-fimc: Allow defining number of sensors at runtime
>       s5p-fimc: Add a platform data entry for MIPI-CSI data alignment
>       s5p-fimc: Use dynamic debug
>       s5p-fimc: Fix G_FMT ioctl handler
> 
>  Documentation/DocBook/media-entities.tmpl    |    1 +
>  Documentation/DocBook/v4l/nv12mt.gif         |  Bin 0 -> 2108 bytes
>  Documentation/DocBook/v4l/nv12mt_example.gif |  Bin 0 -> 6858 bytes
>  Documentation/DocBook/v4l/pixfmt-nv12mt.xml  |   74 +++++++
>  Documentation/DocBook/v4l/pixfmt.xml         |    1 +
>  drivers/media/video/s5p-fimc/fimc-capture.c  |   99 ++++------
>  drivers/media/video/s5p-fimc/fimc-core.c     |  266 ++++++++++++++------------
>  drivers/media/video/s5p-fimc/fimc-core.h     |   50 ++++--
>  drivers/media/video/s5p-fimc/fimc-reg.c      |    6 +-
>  drivers/media/video/videobuf2-core.c         |    9 +-
>  drivers/media/video/videobuf2-dma-sg.c       |    2 +
>  include/media/s5p_fimc.h                     |    9 +-
>  12 files changed, 307 insertions(+), 210 deletions(-)
>  create mode 100644 Documentation/DocBook/v4l/nv12mt.gif
>  create mode 100644 Documentation/DocBook/v4l/nv12mt_example.gif
>  create mode 100644 Documentation/DocBook/v4l/pixfmt-nv12mt.xml
> 

-- 
Sylwester Nawrocki
Samsung Poland R&D Center

      reply	other threads:[~2011-03-08 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 10:53 [GIT PULL FOR 2.6.39] s5p-fimc driver and videobuf2 fixes Sylwester Nawrocki
2011-03-08 16:36 ` Sylwester Nawrocki [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=4D765B0F.8090803@samsung.com \
    --to=s.nawrocki@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mchehab@infradead.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