From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] omap board updates for v3.1 merge window
Date: Fri, 8 Jul 2011 03:25:21 -0700 [thread overview]
Message-ID: <20110708102521.GS5783@atomide.com> (raw)
In-Reply-To: <201107081054.01295.arnd@arndb.de>
* Arnd Bergmann <arnd@arndb.de> [110708 01:49]:
> On Friday 08 July 2011 10:30:42 Tony Lindgren wrote:
> >
> > * Arnd Bergmann <arnd@arndb.de> [110707 13:36]:
> > > On Thursday 07 July 2011 18:29:11 Tony Lindgren wrote:
> > > > Please pull omap board updates from:
> > > >
> > > > git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git devel-board
> > > >
> > > > These are currently on top of the fixes you pulled earlier but
> > > > could be also rebased on the earlier cleanup if you prefer that.
> > >
> > > I would generally prefer them to be independent, even if that causes
> > > minor conflicts. If some branches are built on top of others, that
> > > mainly means I have to remember the order in which to send them
> > > upstream, and my memory for these things is limited.
> >
> > Sure. So let's wait on this one a bit. I'll send you some more cleanup
> > first as I just noticed that the TWL cleanup series will conflict with
> > these patches.
>
> Sorry for being unclear, I forgot to say that I did in fact pull your tree
> already.
OK no problem that's fine with me.
BTW, looks like your tree is no longer showing up on kernel.org?
> > I need to base these board files on all the cleanup though, otherwise
> > things will get messy with merge and build conflicts.
> >
> > Unfortunately there will be dependencies between branches until we
> > have the driver probe and bus (hwmod) code initializing things
> > using device tree data..
>
> I already need to stage things out a bit, because the omap fixes
> depend on the omap cleanups, while the imx cleanups depend on the
> pxa fixes. So it's likely going to be something like
>
> * fixes
> * cleanup
> * more fixes
> * more cleanup
> * new subarchitectures
> * new boards
> * wait for devicetree to get pulled in
> * more cleanups based on device tree
> * other new features
It's getting messy :)
Tony
next prev parent reply other threads:[~2011-07-08 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 16:29 [GIT PULL] omap board updates for v3.1 merge window Tony Lindgren
2011-07-07 20:40 ` Arnd Bergmann
2011-07-07 22:10 ` [PATCH] ARM: omap2: cm-t3730: convert boot_params to atag_offset Igor Grinberg
2011-07-08 8:30 ` [GIT PULL] omap board updates for v3.1 merge window Tony Lindgren
2011-07-08 8:54 ` Arnd Bergmann
2011-07-08 10:25 ` Tony Lindgren [this message]
2011-07-08 11:11 ` Arnd Bergmann
2011-07-08 11:33 ` 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=20110708102521.GS5783@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).