All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>,
	hemahk@ti.com, linux-omap@vger.kernel.org
Subject: Re: OMAP2-only kernel compile broken
Date: Mon, 11 Jul 2011 01:26:50 -0700	[thread overview]
Message-ID: <20110711082650.GN5783@atomide.com> (raw)
In-Reply-To: <20110711064341.GF2680@legolas.emea.dhcp.ti.com>

* Felipe Balbi <balbi@ti.com> [110710 23:38]:
> On Mon, Jul 11, 2011 at 12:31:30AM -0600, Paul Walmsley wrote:
> > On Mon, 11 Jul 2011, Felipe Balbi wrote:
> > 
> > > What on earth is arm-soc omap/cleanup branch ? I generally base my
> > > patches off of Linus' tags. This one in particular was based off of
> > > 3.0-rc6 (or -rc5, can't quite remember). Where is this particular branch
> > > I should base off ?
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/arm/linux-arm-soc.git 
> > 
> > This is Tony's new upstream tree.
> > 
> > Branch is 'omap/cleanup' in this case.

Please don't use those branches for basing patches unless specifically
agreed on.

> Ok, thanks for letting me know.
> 
> Tony, should we *always* base patches for you off of that tree ??

No please don't. Arnd will merge things into those branches to build
his topic specif branches for merging. Always use mainline Linux tags
where possible, or static branches in linux-omap tree that have been
specifically pointed out.

We want to keep dependencies to other trees minimal as they may pull
in other patches too. It also makes it harder to keep track of the
the omap specific code, and makes it harder to do topic specific pull
requests easily.

For example, most patches done against current devel-board should
merge fine with everything else.

Regards,

Tony

  reply	other threads:[~2011-07-11  8:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10  1:57 OMAP2-only kernel compile broken Paul Walmsley
2011-07-10  9:52 ` Felipe Balbi
2011-07-10 10:35   ` Santosh Shilimkar
2011-07-10 11:43   ` Paul Walmsley
2011-07-11  6:21     ` Felipe Balbi
2011-07-11  6:31       ` Paul Walmsley
2011-07-11  6:42         ` Paul Walmsley
2011-07-11  6:43         ` Felipe Balbi
2011-07-11  8:26           ` Tony Lindgren [this message]
2011-07-11  9:24             ` Felipe Balbi
2011-08-15 15:44               ` Paul Walmsley
2011-08-15 16:02                 ` Felipe Balbi
2011-07-11  6:57     ` Felipe Balbi

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=20110711082650.GN5783@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=hemahk@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.