linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Andrew Morton <akpm@linux-foundation.org>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-fbdev-devel@lists.sourceforge.net"
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [GIT PULL]: OMAP2/3 Display Subsystem
Date: Wed, 23 Sep 2009 09:42:24 +0300	[thread overview]
Message-ID: <1253688144.14841.7.camel@tubuntu> (raw)
In-Reply-To: <20090922130304.ffe24448.akpm@linux-foundation.org>

On Tue, 2009-09-22 at 22:03 +0200, ext Andrew Morton wrote:
> On Tue, 22 Sep 2009 15:29:48 +0300
> Tomi Valkeinen <tomi.valkeinen@nokia.com> wrote:
> 
> > Linus,
> > 
> > Here's the new display subsystem and framebuffer driver for OMAP2/3.
> > 
> > The driver has been reviewed on linux-omap and linux-fbdev-devel, and is in
> > use, for example, on N900, Beagle Board and Overo boards. We have an ACK for
> > the OMAP parts from Tony Lindgren, who maintains the OMAP platform.
> > 
> > We have gotten positive feedback about the driver, for example in this thread:
> > http://marc.info/?l=linux-kernel&m=125171081901820&w=2
> > 
> > The driver is actively maintained and developed further, and I have already a
> > bunch of patches on top of these patches, but I would like to get the big core
> > driver merged first. After the driver is merged, other people can send patches
> > to LCD drivers and board files to enable the new display subsystem on their
> > boards.
> > 
> > Andrew said 2-3 weeks ago that he'll merge the driver (after he has looked
> > through it), but he hasn't responded since then. I'm guessing he's quite busy.
> 
> That's because it came very late and conflicts considerably with
> changes which are already pending.
> 
> > Please pull the new OMAP2/3 display subsystem driver from:
> > 
> >   git://gitorious.org/linux-omap-dss2/linux.git for-linus
> > 
> 
> Confused.  These conflicts heavily with the changes which I've already
> queued, does it not?  Ones which were queued way earlier than this
> material.
> 
> If so, why on earth did you send a pull request, knowing that it would
> trash my tree?

Ah, my mistake. I'm new to getting patches merged and the process
involved. Somehow I thought the patches you have went already in, and as
I didn't get any replies for couple of week, I pursued another route.
Sorry about the confusion.

Let's continue this with less audience, no need to bother everyone with
this.

 Tomi

  reply	other threads:[~2009-09-23  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 12:29 [GIT PULL]: OMAP2/3 Display Subsystem Tomi Valkeinen
2009-09-22 12:33 ` Artem Bityutskiy
2009-09-22 14:33   ` Tony Lindgren
2009-09-22 20:03 ` Andrew Morton
2009-09-23  6:42   ` Tomi Valkeinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-09 16:53 Tomi Valkeinen
2009-12-11  5:49 ` Artem Bityutskiy

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=1253688144.14841.7.camel@tubuntu \
    --to=tomi.valkeinen@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=torvalds@linux-foundation.org \
    /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).