public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Archit Taneja <archit@ti.com>
To: Kamil Debski <k.debski@samsung.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: [GIT PULL for 3.15 fixes] VPE fixes
Date: Mon, 7 Apr 2014 15:01:29 +0530	[thread overview]
Message-ID: <53427071.7080509@ti.com> (raw)

Hi Kamil,

Since the VPE m2m patch set couldn't make it on time, I've separated out 
the fixes from the series so that they can be taken in one of the 
3.15-rc series.

Thanks,
Archit

The following changes since commit a83b93a7480441a47856dc9104bea970e84cda87:

   [media] em28xx-dvb: fix PCTV 461e tuner I2C binding (2014-03-31 
08:02:16 -0300)

are available in the git repository at:

   git://github.com/boddob/linux.git vpe-fixes-315-rc

for you to fetch changes up to 3c7d629f0aa98ed587306913831e5a8968504f7a:

   v4l: ti-vpe: retain v4l2_buffer flags for captured buffers 
(2014-04-07 12:56:47 +0530)

----------------------------------------------------------------
Archit Taneja (9):
       v4l: ti-vpe: Make sure in job_ready that we have the needed 
number of dst_bufs
       v4l: ti-vpe: Use video_device_release_empty
       v4l: ti-vpe: Allow usage of smaller images
       v4l: ti-vpe: report correct capabilities in querycap
       v4l: ti-vpe: Use correct bus_info name for the device in querycap
       v4l: ti-vpe: Fix initial configuration queue data
       v4l: ti-vpe: zero out reserved fields in try_fmt
       v4l: ti-vpe: Set correct field parameter for output and capture 
buffers
       v4l: ti-vpe: retain v4l2_buffer flags for captured buffers

  drivers/media/platform/ti-vpe/vpe.c | 45 
++++++++++++++++++++++++++-----------
  1 file changed, 32 insertions(+), 13 deletions(-)

             reply	other threads:[~2014-04-07  9:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  9:31 Archit Taneja [this message]
2014-04-07 14:41 ` [GIT PULL for 3.15 fixes] VPE fixes Kamil Debski

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=53427071.7080509@ti.com \
    --to=archit@ti.com \
    --cc=k.debski@samsung.com \
    --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