From: Andrew Morton <akpm@linux-foundation.org>
To: tomi.valkeinen@nokia.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-fbdev-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: OMAP2/3 Display Subsystem merging
Date: Wed, 23 Sep 2009 00:10:28 -0700 [thread overview]
Message-ID: <20090923001028.bfe04739.akpm@linux-foundation.org> (raw)
In-Reply-To: <1253689449.14841.29.camel@tubuntu>
On Wed, 23 Sep 2009 10:04:09 +0300 Tomi Valkeinen <tomi.valkeinen@nokia.com> wrote:
> Hi,
>
> How can we proceed with the OMAP DSS2 merging? I can take the old omapfb
> patches you have to my tree, and give that tree to you as one set, or I
> can base the DSS2 on top of your tree. If that's ok, where can I find
> the patches or your tree?
Wait for -rc1 (or tomorrow's mainline, probably), redo and retest the
patches, send them out for review and integration.
prev parent reply other threads:[~2009-09-23 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 7:04 OMAP2/3 Display Subsystem merging Tomi Valkeinen
2009-09-23 7:10 ` Andrew Morton [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=20090923001028.bfe04739.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@nokia.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).