public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@nokia.com>
Cc: ext Mike Rapoport <mike@compulab.co.il>,
	"ext Hiremath, Vaibhav" <hvaibhav@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Moving board patches from DSS2 to linux-omap
Date: Fri, 12 Feb 2010 12:42:18 -0800	[thread overview]
Message-ID: <20100212204218.GT21755@atomide.com> (raw)
In-Reply-To: <1265971459.2433.285.camel@tubuntu.research.nokia.com>

* Tomi Valkeinen <tomi.valkeinen@nokia.com> [100212 02:38]:
> On Thu, 2010-02-11 at 19:52 +0100, ext Tony Lindgren wrote:
> > * Tomi Valkeinen <tomi.valkeinen@nokia.com> [100211 03:59]:
> > > On Thu, 2010-02-11 at 12:50 +0100, ext Mike Rapoport wrote:
> > > > Tomi Valkeinen wrote:
> > > > > Hi,
> > > > > 
> > > > > As discussed previously, board file changes in DSS2 tree cause conflicts
> > > > > with linux-omap easily. There are currently three board file patches in
> > > > > DSS2's for-next branch:
> > > > > 
> > > > > 722a97e4594b2041bbf18d95a913ba6dfaca87f2 omap3: cm-t35: add DSS2 display support
> > > > > 7a56267e775e469c64521179ccc958c8bb661dbf OMAP: AM3517: Enable DSS2 for AM3517EVM board
> > > > > 40e4e67c6dabcb9897b6823cce2297d6c3e78bbd OMAP: Enable DSS2 for OMAP3EVM board
> > > > > 
> > > > > The problem here is of course that DSS2 tree may contain unmerged panel
> > > > > drivers, and those board file changes try to use these new panel
> > > > > drivers.
> > 
> > OK, Tomi, can you please set up a banch against mainline -rc7 with
> > whatever board-*.c dss2 patches you want me to pull? I'll pull them
> > into omap-for-linus, and rebase omap for-next on those.
> 
> Here:
> 
> git://gitorious.org/linux-omap-dss2/linux.git for-tony
> 
> I removed the defconfig changes from the patches, and compile tested.
> I'll add the defconfig changes as separate patches in my tree, and I'll
> push them to Linus only after the board changes from Tony's tree have
> gone through.

Great, thanks, I've pulled it into omap-for-linus branch. Note that we
need to wait for Russell to merge the arm changes first and then I
need merge with that before I can send a pull request because of the
addruart changes that affect most of our multi-omap patches.

So you may want to send the defconfig changes as a separate fix later on
if that allows you to keep your dss2 mergeable without having to worry
about the merging of arm and omap trees.

Regards,

Tony

  reply	other threads:[~2010-02-12 20:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 10:29 Moving board patches from DSS2 to linux-omap Tomi Valkeinen
2010-02-11 11:50 ` Mike Rapoport
2010-02-11 12:04   ` Tomi Valkeinen
2010-02-11 18:52     ` Tony Lindgren
2010-02-12 10:44       ` Tomi Valkeinen
2010-02-12 20:42         ` Tony Lindgren [this message]
2010-02-13 10:34         ` Hiremath, Vaibhav
2010-02-13 10:43         ` Hiremath, Vaibhav
2010-02-15  7:43           ` Tomi Valkeinen

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=20100212204218.GT21755@atomide.com \
    --to=tony@atomide.com \
    --cc=hvaibhav@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --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