From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL FOR v4.6] Fixes, enhancement and move 3 soc-camera drivers to staging
Date: Thu, 3 Mar 2016 12:25:00 +0100 [thread overview]
Message-ID: <56D81F0C.1010406@xs4all.nl> (raw)
In-Reply-To: <20160303074017.750ff14c@recife.lan>
On 03/03/16 11:40, Mauro Carvalho Chehab wrote:
> Em Fri, 26 Feb 2016 08:45:48 +0100
> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
>
>> The following changes since commit 3915d367932609f9c0bdc79c525b5dd5a806ab18:
>>
>> [media] ttpci: cleanup a bogus smatch warning (2016-02-23 07:26:22 -0300)
>>
>> are available in the git repository at:
>>
>> git://linuxtv.org/hverkuil/media_tree.git for-v4.6f
>>
>> for you to fetch changes up to 16295c7590a2272050fb1ae935ce65860f930351:
>>
>> soc_camera/mx3_camera.c: move to staging in preparation, for removal (2016-02-26 08:21:05 +0100)
>>
>> ----------------------------------------------------------------
>> Hans Verkuil (5):
>> tc358743: use - instead of non-ascii wide-dash character
>> vivid: support new multiplanar YUV formats
>> soc_camera/omap1: move to staging in preparation for removal
>> soc_camera/mx2_camera.c: move to staging in preparation, for removal
>> soc_camera/mx3_camera.c: move to staging in preparation, for removal
>>
>> Philipp Zabel (2):
>> coda: add support for native order firmware files with Freescale header
>> coda: add support for firmware files named as distributed by NXP
>>
>> Ulrich Hecht (1):
>> adv7604: fix SPA register location for ADV7612
>>
>> drivers/media/i2c/adv7604.c | 3 +-
>> drivers/media/i2c/tc358743.c | 30 +++++-----
>> drivers/media/platform/coda/coda-common.c | 96 ++++++++++++++++++++++++++------
>> drivers/media/platform/coda/coda.h | 3 +-
>> drivers/media/platform/soc_camera/Kconfig | 28 ----------
>> drivers/media/platform/soc_camera/Makefile | 3 -
>> drivers/media/platform/vivid/vivid-tpg.c | 32 +++++++++++
>> drivers/media/platform/vivid/vivid-vid-common.c | 39 ++++++++++++-
>> drivers/staging/media/Kconfig | 6 ++
>> drivers/staging/media/Makefile | 3 +
>> drivers/staging/media/mx2/Kconfig | 12 ++++
>> drivers/staging/media/mx2/Makefile | 3 +
>> .../{media/platform/soc_camera => staging/media/mx2}/mx2_camera.c | 0
>> drivers/staging/media/mx3/Kconfig | 15 +++++
>> drivers/staging/media/mx3/Makefile | 3 +
>> .../{media/platform/soc_camera => staging/media/mx3}/mx3_camera.c | 0
>> drivers/staging/media/omap1/Kconfig | 13 +++++
>> drivers/staging/media/omap1/Makefile | 3 +
>> .../platform/soc_camera => staging/media/omap1}/omap1_camera.c | 0
>> 19 files changed, 224 insertions(+), 68 deletions(-)
>> create mode 100644 drivers/staging/media/mx2/Kconfig
>> create mode 100644 drivers/staging/media/mx2/Makefile
>> rename drivers/{media/platform/soc_camera => staging/media/mx2}/mx2_camera.c (100%)
>> create mode 100644 drivers/staging/media/mx3/Kconfig
>> create mode 100644 drivers/staging/media/mx3/Makefile
>> rename drivers/{media/platform/soc_camera => staging/media/mx3}/mx3_camera.c (100%)
>> create mode 100644 drivers/staging/media/omap1/Kconfig
>> create mode 100644 drivers/staging/media/omap1/Makefile
>> rename drivers/{media/platform/soc_camera => staging/media/omap1}/omap1_camera.c (100%)
>
> Please send a followup patch adding README instructions for those
> drivers that got moved to staging. We don't want to receive
> trivial fixup patches for this stuff, but, instead, if one
> wants them to go promoted again, it should be converted to work
> without soc_camera.
Done.
Regards,
Hans
next prev parent reply other threads:[~2016-03-03 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 7:45 [GIT PULL FOR v4.6] Fixes, enhancement and move 3 soc-camera drivers to staging Hans Verkuil
2016-03-03 10:40 ` Mauro Carvalho Chehab
2016-03-03 11:25 ` Hans Verkuil [this message]
2016-03-03 21:30 ` Mauro Carvalho Chehab
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=56D81F0C.1010406@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.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 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.