From: Arnd Bergmann <arnd@arndb.de>
To: Tony Lindgren <tony@atomide.com>
Cc: Olof Johansson <olof@lixom.net>,
Benoit Cousson <b-cousson@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Florian Vaussard <florian.vaussard@epfl.ch>,
Vaibhav Hiremath <hvaibhav@ti.com>,
Eduardo Valentin <eduardo.valentin@ti.com>,
Mohammed Afzal <afzal@ti.com>, Paul Walmsley <paul@pwsan.com>,
Roger Quadros <rogerq@ti.com>
Subject: Re: [GIT PULL] ARM: OMAP: Device Tree for 3.11
Date: Thu, 20 Jun 2013 21:48:41 +0200 [thread overview]
Message-ID: <201306202148.41464.arnd@arndb.de> (raw)
In-Reply-To: <20130620064541.GE5523@atomide.com>
On Thursday 20 June 2013, Tony Lindgren wrote:
> * Benoit Cousson <b-cousson@ti.com> [130619 16:10]:
> > Hi Tony,
> >
> > Please pull the following commits for OMAP Device Tree for v3.11.
> >
> > It does contains as well 2 clock data patches, I hope it will not generate any conflict with Paul's tree.
> >
> > Special thanks to Florian for his nice cleanup using the C preprocessor.
>
> It's best that Arnd and Olof take this pull request directly as we're
> getting so close to the merge window. These patches should be pretty
> much independent of the other branches I've sent, and are needed to
> keep omap4 booting now that we've flipped the switch for omap4 to be
> DT only.
>
Would someone provide a merge description for this? I just noticed
that it's not a signed tag, and there are lots of patches in it,
so I'd rather not have to come up with something myself.
Arnd
next prev parent reply other threads:[~2013-06-20 19:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 23:04 [GIT PULL] ARM: OMAP: Device Tree for 3.11 Benoit Cousson
2013-06-20 6:45 ` Tony Lindgren
2013-06-20 9:05 ` Arnd Bergmann
2013-06-20 19:48 ` Arnd Bergmann [this message]
2013-06-20 20:48 ` Cousson, Benoit
2013-06-20 21:03 ` Arnd Bergmann
2013-06-20 20:34 ` 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=201306202148.41464.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=afzal@ti.com \
--cc=b-cousson@ti.com \
--cc=eduardo.valentin@ti.com \
--cc=florian.vaussard@epfl.ch \
--cc=hvaibhav@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul@pwsan.com \
--cc=rogerq@ti.com \
--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