linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP2+: Add AM335x and AM3517/05 EVM DT support
Date: Sat, 12 May 2012 10:15:04 -0700	[thread overview]
Message-ID: <20120512171503.GL5140@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA23806@DBDE01.ent.ti.com>

* Hiremath, Vaibhav <hvaibhav@ti.com> [120512 01:26]:
> On Sat, May 12, 2012 at 01:26:20, Tony Lindgren wrote:
> > Hi,
> > 
> > * Cousson, Benoit <b-cousson@ti.com> [120511 05:51]:
> > > Hi Tony,
> > > 
> > > Here are some remaining DT patches I was not able to push at 3.4 due to some missing dependency.
> > > It applies now fine on top of lo/dt branch.
> > 
> > It seems that there are still patches being discussed for those SoCs
> > and we're pretty much done for this merge window. So unless things
> > drag on to -rc8, I'd say we just need to postpone merging new things
> > and merge them early around -rc2.
> > 
> 
> Oops...
> It seems like I missed this merge window as well...

We can still queue these into linux-omap for testing as
soon as the patches are ready.

In general, for anything more intrusive we want to have
the patches sitting in linux-omap master branch and then
in linux-next for at least a week. Then merging them into
mainline tree is usually safe to do. The reason for this is
that mainline kernel is our stable tree, not our
development tree.

We just need to queue most of things between -rc2 and
-rc4 into the arm-soc tree, and have any issues fixed up
before the merge window. Trying to cram development
branches in around -rc6 just causes us a huge maintenance
nightmare trying to fix up things in the mainline tree
between -rc1 and -rc4.

Cheers,

Tony

  reply	other threads:[~2012-05-12 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 12:47 [GIT PULL] ARM: OMAP2+: Add AM335x and AM3517/05 EVM DT support Cousson, Benoit
2012-05-11 19:56 ` Tony Lindgren
2012-05-12  8:22   ` Hiremath, Vaibhav
2012-05-12 17:15     ` Tony Lindgren [this message]
2012-05-15  6:05       ` Hiremath, Vaibhav
2012-05-29  6:16 ` Hiremath, Vaibhav
2012-06-05  7:57 ` Tony Lindgren

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=20120512171503.GL5140@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).