From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Tony Lindgren <tony@atomide.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Olof Johansson <olof@lixom.net>,
linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [GIT PULL] ARM: OMAP: i2c, gpio, spi, regulator and mmc DTS updates
Date: Thu, 15 Mar 2012 08:01:12 +0000 [thread overview]
Message-ID: <201203150801.13183.arnd@arndb.de> (raw)
In-Reply-To: <20120315004638.GW12083@atomide.com>
On Thursday 15 March 2012, Tony Lindgren wrote:
> * Cousson, Benoit <b-cousson@ti.com> [120314 16:41]:
> > Hi Tony,
> >
> > Here are the remaining DTS patches for 3.4.
> >
> > On top of the previous pull request, I just added the MMC DTS since the driver adaptation just got queued.
> >
> > It will be still be good to have that for 3.4 if possible, otherwise we will
> > have a bunch of drivers DT adapted but no DTS file to use them :-(
>
> This might be doable as a follow-up patch series at the end
> of the merge window or at -rc1 when the related driver changes
> have been merged.
>
> Arnd and Olof, what do you guys think?
I'll have to look at the patches more closely, but from the diffstat it definitely
looks ok for a later merge once the driver is in. If you can rebase the branch on
top of the mmc tree (or the merge of that tree with whatever else is needed), it
should give us a bisectable history and I can stick it into a late/* branch right
away.
Arnd
next prev parent reply other threads:[~2012-03-15 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 23:39 [GIT PULL] ARM: OMAP: i2c, gpio, spi, regulator and mmc DTS updates Cousson, Benoit
2012-03-15 0:46 ` Tony Lindgren
2012-03-15 8:01 ` Arnd Bergmann [this message]
2012-03-29 14:08 ` Cousson, Benoit
2012-03-29 18:31 ` Olof Johansson
2012-04-15 1:19 ` Olof Johansson
2012-04-16 18:00 ` Tony Lindgren
2012-04-16 20:29 ` Cousson, Benoit
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=201203150801.13183.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--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