linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prabhakar Lad <prabhakar.csengg@gmail.com>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	dlos <davinci-linux-open-source@linux.davincidsp.com>
Subject: [GIT PULL FOR v3.17] Davinci Media
Date: Wed, 16 Jul 2014 21:06:18 +0100	[thread overview]
Message-ID: <CA+V-a8unPvRPfoDNBsyyCAPCva7HokysuqG5QhcMuMrTbsCWaw@mail.gmail.com> (raw)

Hi Mauro,

Please pull the following patches for davinci media which include
trivial cleanups.

Thanks,
--Prabhakar Lad

The following changes since commit 3c0d394ea7022bb9666d9df97a5776c4bcc3045c:

  [media] dib8000: improve the message that reports per-layer locks
(2014-07-07 09:59:01 -0300)

are available in the git repository at:

  git://linuxtv.org/mhadli/v4l-dvb-davinci_devices.git davinci_media

for you to fetch changes up to c219eb5c0fa71e11793cdc1456da8fe04f76b5ff:

  staging: media: davinci_vpfe: fix checkpatch warning (2014-07-16
20:48:18 +0100)

----------------------------------------------------------------
Andrey Utkin (1):
      davinci-vpfe: Fix retcode check

Dan Carpenter (1):
      davinci: vpfe: dm365: remove duplicate RSZ_LPF_INT_MASK

Lad, Prabhakar (2):
      media: davinci_vpfe: dm365_resizer: fix sparse warning
      staging: media: davinci_vpfe: fix checkpatch warning

 drivers/staging/media/davinci_vpfe/dm365_ipipe.c    | 2 ++
 drivers/staging/media/davinci_vpfe/dm365_ipipe_hw.c | 2 +-
 drivers/staging/media/davinci_vpfe/dm365_ipipe_hw.h | 1 -
 drivers/staging/media/davinci_vpfe/dm365_resizer.c  | 4 ++--
 4 files changed, 5 insertions(+), 4 deletions(-)

                 reply	other threads:[~2014-07-16 20:06 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=CA+V-a8unPvRPfoDNBsyyCAPCva7HokysuqG5QhcMuMrTbsCWaw@mail.gmail.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.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;
as well as URLs for NNTP newsgroup(s).