linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	ext Tony Lindgren <tony@atomide.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-fbdev-devel@lists.sourceforge.net"
	<linux-fbdev-devel@lists.sourceforge.net>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: [PATCH 00/19] OMAP: DSS2 v5 intro
Date: Wed, 11 Nov 2009 11:44:01 +0200	[thread overview]
Message-ID: <1257932641.20378.77.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <1257929140.20378.51.camel@tubuntu.research.nokia.com>

On Wed, 2009-11-11 at 09:45 +0100, Valkeinen Tomi (Nokia-D/Helsinki)
wrote:
> On Tue, 2009-11-10 at 13:40 +0100, Artem Bityutskiy wrote:
> > Tomi,
> > 
> > could you please kindly ask Stephen (CCed) to include the DSS2 tree into
> > linux-next, because you are going to merge it the next merge window, and
> > there does not seem to be any blocker for this.
> > 
> > Being in linux-next for a while is really important.
> 
> Stephen, would this be possible? DSS2 driver is rather big piece of
> code, even if it's quite isolated, so it would be nice to have it in
> linux-next.
> 
> What does it require from me? A git tree, obviously, but what should it
> be based on?

Ah, I just realized that DSS2 patches depend on patches from Tony's
tree. I guess I should base my tree on top of some Tony's tree that is
going to linux-next?

 Tomi

  reply	other threads:[~2009-11-11  9:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 11:45 [PATCH 00/19] OMAP: DSS2 v5 intro Tomi Valkeinen
2009-11-09 11:45 ` [PATCH 01/19] OMAP2: Add funcs for writing SMS_ROT_* registers Tomi Valkeinen
2009-11-09 11:45   ` [PATCH 02/19] OMAP: OMAPFB: split omapfb.h Tomi Valkeinen
2009-11-09 11:45     ` [PATCH 03/19] OMAP: OMAPFB: add omapdss device Tomi Valkeinen
2009-11-09 11:45       ` [PATCH 04/19] OMAP: Add VRAM manager Tomi Valkeinen
2009-11-09 11:45         ` [PATCH 05/19] OMAP: Add support for VRFB rotation engine Tomi Valkeinen
2009-11-09 11:45           ` [PATCH 06/19] OMAP: DSS2: Documentation for DSS2 Tomi Valkeinen
2009-11-09 11:45             ` [PATCH 07/19] OMAP: DSS2: Display Subsystem Driver core Tomi Valkeinen
2009-11-09 11:45               ` [PATCH 08/19] OMAP: DSS2: Add more core files Tomi Valkeinen
2009-11-09 11:45                 ` [PATCH 09/19] OMAP: DSS2: DISPC Tomi Valkeinen
2009-11-09 11:45                   ` [PATCH 10/19] OMAP: DSS2: DPI driver Tomi Valkeinen
2009-11-09 11:45                     ` [PATCH 11/19] OMAP: DSS2: Video encoder driver Tomi Valkeinen
2009-11-09 11:45                       ` [PATCH 12/19] OMAP: DSS2: RFBI driver Tomi Valkeinen
2009-11-09 11:45                         ` [PATCH 13/19] OMAP: DSS2: SDI driver Tomi Valkeinen
2009-11-09 11:45                           ` [PATCH 14/19] OMAP: DSS2: DSI driver Tomi Valkeinen
2009-11-09 11:45                             ` [PATCH 15/19] OMAP: DSS2: omapfb driver Tomi Valkeinen
2009-11-09 11:45                               ` [PATCH 16/19] OMAP: DSS2: Add DPI panel drivers Tomi Valkeinen
2009-11-09 11:45                                 ` [PATCH 17/19] OMAP: DSS2: Taal DSI command mode panel driver Tomi Valkeinen
2009-11-09 11:45                                   ` [PATCH 18/19] OMAP: SDP: Enable DSS2 for OMAP3 SDP board Tomi Valkeinen
2009-11-09 11:45                                     ` [PATCH 19/19] MAINTAINERS: Add OMAP2/3 DSS and OMAPFB maintainer Tomi Valkeinen
2009-11-10 12:40 ` [PATCH 00/19] OMAP: DSS2 v5 intro Artem Bityutskiy
2009-11-11  8:45   ` Tomi Valkeinen
2009-11-11  9:44     ` Tomi Valkeinen [this message]
2009-11-11 18:42       ` Tony Lindgren
2009-11-12  5:03         ` Artem Bityutskiy
2009-11-12 18:08           ` Tony Lindgren
2009-11-12  5:10         ` Stephen Rothwell
2009-11-12 18:14           ` Tony Lindgren
2009-11-12 20:48             ` Stephen Rothwell
2009-11-13  9:56               ` Tomi Valkeinen
2009-11-13 17:59                 ` Tony Lindgren
2009-11-15 22:38                   ` Stephen Rothwell

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=1257932641.20378.77.camel@tubuntu.research.nokia.com \
    --to=tomi.valkeinen@nokia.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tony@atomide.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).