From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Hans Verkuil <hansverk@cisco.com>,
devel@driverdev.osuosl.org,
DLOS <davinci-linux-open-source@linux.davincidsp.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Prabhakar Lad <prabhakar.lad@ti.com>,
Prabhakar Lad <prabhakar.csengg@gmail.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Manjunath Hadli <manjunath.hadli@ti.com>,
LMML <linux-media@vger.kernel.org>
Subject: Re: [PATCH v3 0/9] Media Controller capture driver for DM365
Date: Wed, 28 Nov 2012 20:30:04 +0100 [thread overview]
Message-ID: <50B6663C.6080800@samsung.com> (raw)
In-Reply-To: <20121128122227.GX6186@mwanda>
On 11/28/2012 01:22 PM, Dan Carpenter wrote:
> In the end this is just a driver, and I don't especially care. But
> it's like not just this one which makes me frustrated. I really
> believe in linux-next and I think everything should spend a couple
> weeks there before being merged.
Couple of weeks in linux-next plus a couple of weeks of final patch
series version awaiting to being reviewed and picked up by a maintainer
makes almost entire kernel development cycle. These are huge additional
delays, especially in the embedded world. Things like these certainly
aren't encouraging for moving over from out-of-tree to the mainline
development process. And in this case we are talking only about merging
driver to the staging tree...
--
Thanks,
Sylwester
next prev parent reply other threads:[~2012-11-28 19:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 10:42 [PATCH v3 0/9] Media Controller capture driver for DM365 Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 1/9] davinci: vpfe: add v4l2 capture driver with media interface Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 2/9] davinci: vpfe: add v4l2 video driver support Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 3/9] davinci: vpfe: dm365: add IPIPEIF driver based on media framework Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 4/9] davinci: vpfe: dm365: add ISIF " Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 5/9] davinci: vpfe: dm365: add IPIPE support for media controller driver Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 6/9] davinci: vpfe: dm365: add IPIPE hardware layer support Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 7/9] davinci: vpfe: dm365: resizer driver based on media framework Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 8/9] davinci: vpfe: dm365: add build infrastructure for capture driver Prabhakar Lad
2012-11-28 10:42 ` [PATCH v3 9/9] davinci: vpfe: Add documentation and TODO Prabhakar Lad
2012-11-28 11:22 ` Mauro Carvalho Chehab
2012-11-28 13:00 ` Laurent Pinchart
2012-11-28 19:35 ` Mauro Carvalho Chehab
2012-11-29 3:08 ` Prabhakar Lad
2012-11-28 20:00 ` Sakari Ailus
2012-11-28 11:45 ` [PATCH v3 0/9] Media Controller capture driver for DM365 Dan Carpenter
2012-11-28 11:56 ` Hans Verkuil
2012-11-28 12:18 ` Mauro Carvalho Chehab
2012-11-28 17:22 ` Greg Kroah-Hartman
2012-11-28 19:18 ` Hans Verkuil
2012-11-28 19:30 ` Greg Kroah-Hartman
2012-11-29 7:43 ` Hans Verkuil
2012-11-29 10:39 ` Mauro Carvalho Chehab
2012-11-29 12:45 ` Manjunath Hadli
2012-11-29 16:38 ` Mauro Carvalho Chehab
2012-11-28 21:04 ` Dan Carpenter
2012-11-28 12:22 ` Dan Carpenter
2012-11-28 19:30 ` Sylwester Nawrocki [this message]
2012-11-28 20:46 ` Greg Kroah-Hartman
2012-11-28 21:29 ` Dan Carpenter
2012-11-28 23:47 ` Sylwester Nawrocki
2012-11-29 7:40 ` Hans Verkuil
2012-11-28 20:04 ` Sakari Ailus
2012-11-29 10:12 ` Laurent Pinchart
2012-11-30 9:47 ` Sakari Ailus
2012-11-30 9:54 ` Hans Verkuil
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=50B6663C.6080800@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hans.verkuil@cisco.com \
--cc=hansverk@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=manjunath.hadli@ti.com \
--cc=mchehab@redhat.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.lad@ti.com \
--cc=sakari.ailus@iki.fi \
/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