linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: lo-ml <linux-omap@vger.kernel.org>,
	lfbdev-ml <linux-fbdev@vger.kernel.org>
Subject: Re: [GIT PULL] OMAP DSS updates for 2.6.40
Date: Tue, 24 May 2011 09:37:03 +0000	[thread overview]
Message-ID: <1306229823.2194.14.camel@deskari> (raw)
In-Reply-To: <20110524063803.GC11986@linux-sh.org>

On Tue, 2011-05-24 at 15:38 +0900, Paul Mundt wrote:
> On Mon, May 23, 2011 at 02:43:24PM +0300, Tomi Valkeinen wrote:
> > Here are the OMAP Display Subsystem updates for 2.6.40.
> > 
> > Most of the patches are OMAP4 related, either fixing the old code to
> > allow us to implement new OMAP4 features, or implementing those new
> > features. Other bigger changes are ULPS power management feature and
> > moving the DSS header file from arch/arm/plat-omap/include to
> > include/video.
> > 
> Pulled and pushed out, thanks. There were a couple of conflicts, so you
> may want to doublecheck to make sure nothing was inadvertently broken.

I wonder where those conflicts came from...

I think this pull request never made into the 39 rcs:

http://www.mail-archive.com/linux-omap@vger.kernel.org/msg48334.html

I should have checked it, but it seems I've missed those. So you had
those patches in fbdev tree, and I had the same patches in my
development tree (which ended up being rebased a bit), and this led to
those conflicts.

But diff between omapdss in my master branch and fbdev master is null,
so the conflicts were resolved correctly.

 Tomi



      reply	other threads:[~2011-05-24  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 11:43 [GIT PULL] OMAP DSS updates for 2.6.40 Tomi Valkeinen
2011-05-24  6:38 ` Paul Mundt
2011-05-24  9:37   ` Tomi Valkeinen [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=1306229823.2194.14.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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).