From: "Cousson, Benoit" <b-cousson@ti.com>
To: Olof Johansson <olof@lixom.net>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org
Subject: Re: [GIT PULL] ARM: OMAP: i2c, gpio, spi, regulator and mmc DTS updates
Date: Mon, 16 Apr 2012 22:29:58 +0200 [thread overview]
Message-ID: <4F8C8146.6070603@ti.com> (raw)
In-Reply-To: <CAOesGMjJMgQF9jUUUMbm22oaEzan6eLW+-kWN9iB85buJxp4Dg@mail.gmail.com>
Hi Olof,
On 4/15/2012 3:19 AM, Olof Johansson wrote:
> Benoit, Tony,
>
> On Thu, Mar 29, 2012 at 11:31 AM, Olof Johansson<olof@lixom.net> wrote:
>> On Thu, Mar 29, 2012 at 7:08 AM, Cousson, Benoit<b-cousson@ti.com> wrote:
>>> FYI, MMC DT adaptation just got merged, I2C, GPIO, SPI, regulator DT
>>> adaptation were already merged before, so it means that this branch can be
>>> merged to take advantage of all the DT adapted drivers.
>>
>> I've pulled this in as late/omap-dt, included in next/dt3 and
>> for-next. I'll let it sit in linux-next for at least one day before
>> it's sent in. Since it's just device tree additions, risk for
>> regressions should be low.
>
> As you've noticed, this didn't make it into 3.4 due to the window
> closing early. :(
Yes, I did :-(
> I've renamed the branch in arm-soc to omap/dt-missed-3.4 and merged it
> into next/dt for the 3.5 merge window.
OK, cool, I was about to ping you about that series. I'll then be able
to use it as a stable base for further OMAP DT patches.
Thanks,
Benoit
prev parent reply other threads:[~2012-04-16 20:29 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
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 [this message]
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=4F8C8146.6070603@ti.com \
--to=b-cousson@ti.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--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