linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Quadros Roger (Nokia-D/Helsinki)" <roger.quadros@nokia.com>,
	Jarkko Nikula <jhnikula@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: linux-next: manual merge of the omap_dss2 tree with the omap tree
Date: Mon, 17 May 2010 10:07:08 +0300	[thread overview]
Message-ID: <1274080028.2307.3.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <20100514190906.GA3428@atomide.com>

On Fri, 2010-05-14 at 21:09 +0200, ext Tony Lindgren wrote:
> * Tomi Valkeinen <tomi.valkeinen@nokia.com> [100512 01:54]:
> > Hi,
> > 
> > On Mon, 2010-05-10 at 22:20 +0200, ext Tony Lindgren wrote:
> > > * Stephen Rothwell <sfr@canb.auug.org.au> [100506 22:05]:
> > > > Hi Tomi,
> > > > 
> > > > Today's linux-next merge of the omap_dss2 tree got a conflict in
> > > > arch/arm/mach-omap2/board-rx51-peripherals.c between commit
> > > > e87da74e34ad151e6ae75ebb7a7bf447f02c0004 ("omap: rx51: Add supplies for
> > > > the tlv320aic3x codec driver") from the omap tree and commit
> > > > a693839eab0292aa234d7a6f48d40389389baebb ("OMAP: RX51: Add "vdds_sdi"
> > > > supply voltage for SDI") from the omap_dss2 tree.
> > > > 
> > > > Just overlapping additions. I fixed it up (see below) and can carry the
> > > > fix as necessary.
> > > 
> > > Thanks again Stephen. We will move the conflicting DSS board-*.c
> > > file changes over to omap for next.
> > > 
> > > Tomi, do you want to do a branch of board-*.c patches for me to
> > > pull, or do you want me to just pick this one?
> > 
> > I think it's ok to pick just this one. It's just adds a regulator
> > supply, and doesn't interfere with anything. I just need to make sure
> > linux-omap's for-next is merged first, before I send my pull request.
> 
> Thanks, I've picked this patch.
>  
> > I made a branch for it, based on linux-omap/for-next:
> > git://gitorious.org/linux-omap-dss2/linux.git for-tony
> > 
> > And I dropped the patch from my for-next branch.
> 
> Tomi, next time please check that your branch is based on
> either the most recent tag by Linus, or in the conflicting
> cases you can base on omap-for-linus branch. Please don't
> base on for-next or other branches that are not yet
> static, we don't want the merge history of duplicate branches.

Oh, that branch was just for you to cherry pick the one patch. My
"normal" branches are based on official tags.

 Tomi



  reply	other threads:[~2010-05-17  7:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  3:43 linux-next: manual merge of the omap_dss2 tree with the omap tree Stephen Rothwell
2010-05-10 20:20 ` Tony Lindgren
2010-05-12  8:59   ` Tomi Valkeinen
2010-05-14 19:09     ` Tony Lindgren
2010-05-17  7:07       ` Tomi Valkeinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-21  3:16 Stephen Rothwell
2011-02-21  8:47 ` Tomi Valkeinen
2011-02-24 21:23   ` Tony Lindgren
2011-02-18  2:25 Stephen Rothwell
2011-02-17  2:10 Stephen Rothwell
2011-02-17  2:10 Stephen Rothwell
2010-02-08  6:25 Stephen Rothwell
2010-02-08  9:29 ` Tomi Valkeinen
2010-02-08 10:57   ` Stephen Rothwell
2010-02-08 11:43     ` Tomi Valkeinen
2010-02-09 16:52   ` Tony Lindgren
2010-02-10  8:20     ` Tomi Valkeinen
2010-02-10  9:52 ` Hiremath, Vaibhav
2010-02-03  4:29 Stephen Rothwell
2010-02-03 12:29 ` Grazvydas Ignotas
2010-02-03 17:12   ` Tony Lindgren
2010-02-04  9:42     ` Tomi Valkeinen
2009-11-16  5:04 Stephen Rothwell
2009-11-16 10:06 ` Tomi Valkeinen
2009-11-16 18:34   ` Tony Lindgren
2009-11-17 10:00     ` Tomi Valkeinen
2009-11-17 23:49       ` Stephen Rothwell
2009-11-17  3:08 ` Sid Boyce

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=1274080028.2307.3.camel@tubuntu.research.nokia.com \
    --to=tomi.valkeinen@nokia.com \
    --cc=jhnikula@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=roger.quadros@nokia.com \
    --cc=sfr@canb.auug.org.au \
    --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;
as well as URLs for NNTP newsgroup(s).