From: Tony Lindgren <tony@atomide.com>
To: David Brownell <david-b@pacbell.net>
Cc: "Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/15] OMAP3 camera driver: V4L2: Adding IOCTL command to get slave private data.
Date: Tue, 2 Sep 2008 15:53:36 -0700 [thread overview]
Message-ID: <20080902225336.GM23085@atomide.com> (raw)
In-Reply-To: <200808311435.47689.david-b@pacbell.net>
* David Brownell <david-b@pacbell.net> [080831 14:36]:
> On Friday 29 August 2008, Aguirre Rodriguez, Sergio Alberto wrote:
> > From: Sakari Ailus <sakari.ailus@nokia.com>
> > Date: Tue, 15 Apr 2008 10:35:15 +0300
> > Subject: [PATCH] Adding IOCTL command to get slave private data.
> >
> > Signed-off-by: Sakari Ailus <sakari.ailus@nokia.com>
> > ---
> > include/media/v4l2-int-device.h | 6 ++++++
> > 1 files changed, 6 insertions(+), 0 deletions(-)
>
> Seeing that series of patches from Felipe makes me wonder why
> these patches shouldn't go *first* to the V4L list ... to help
> avoid letting code sit for a long time in the OMAP tree without
> going upstream.
>
> This particular patch for example is not OMAP-specific.
>
> And in general, the relevant review team for a V4L driver
> (the rest of this series) is the V4L team not the OMAP team.
> And if this driver passes their review, why not just merge
> to mainline right away?
Yeah, this series should go via V4L list.
Tony
next prev parent reply other threads:[~2008-09-02 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 23:23 [PATCH 1/15] OMAP3 camera driver: V4L2: Adding IOCTL command to get slave private data Aguirre Rodriguez, Sergio Alberto
2008-08-31 21:35 ` David Brownell
2008-09-02 22:53 ` Tony Lindgren [this message]
2008-09-02 14:55 ` Zou Tao
2008-09-02 16:15 ` Aguirre Rodriguez, Sergio Alberto
2008-09-05 13:36 ` Zou Tao
2008-09-05 14:44 ` Aguirre Rodriguez, Sergio Alberto
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=20080902225336.GM23085@atomide.com \
--to=tony@atomide.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.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.