From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: Tony Lindgren <tony@atomide.com>,
"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: Mon, 16 Nov 2009 09:38:20 +1100 [thread overview]
Message-ID: <20091116093820.aa5a36b7.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20091113175928.GB3684@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]
Tomi,
On Fri, 13 Nov 2009 09:59:28 -0800 Tony Lindgren <tony@atomide.com> wrote:
>
> > I rebased DSS2 on top of 8171d88089ad63fc442b2bf32af7c18653adc5cb. It
> > can be found from git://gitorious.org/linux-omap-dss2/linux.git for-next
> > branch.
> >
> > I'm ok with Tony pulling DSS2 to his next-branch, or Stephen pulling
> > directly, which ever works easier for you.
>
> I'd rather see Stephen pulling directly from Tomi, that's a good long
> term solution for maintaining the DSS2 code.
OK, I have added that branch to linux-next from today. Thanks for all
the efforts.
Thanks for adding your subsystem tree as a participant of linux-next. As
you may know, this is not a judgment of your code. The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have
been:
* submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him
to fetch). It is allowed to be rebased if you deem it necessary.
--
Cheers,
Stephen Rothwell
sfr@canb.auug.org.au
Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees. You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next. These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc. The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc. If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2009-11-15 22:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 11:45 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
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 [this message]
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=20091116093820.aa5a36b7.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dedekind1@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.com \
--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
all inboxes | Powered by JetHome®