From: Arnd Bergmann <arnd@arndb.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Olof Johansson <olof@lixom.net>,
arm@kernel.org, Linux Kernel list <linux-kernel@vger.kernel.org>,
"linux-arm-kernel" <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
"Jean-Christophe PLAGNIOL-VILLARD" <plagnioj@jcrosoft.com>,
Vinod Koul <vinod.koul@intel.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>
Subject: Re: [GIT PULL] at91: dt for 3.19 #2
Date: Thu, 20 Nov 2014 13:41:29 +0100 [thread overview]
Message-ID: <201411201341.30112.arnd@arndb.de> (raw)
In-Reply-To: <1416415953-31966-1-git-send-email-nicolas.ferre@atmel.com>
On Wednesday 19 November 2014, Nicolas Ferre wrote:
> Another DT pull-request for 3.19. For this one, I had to pull one Vinod's topic
> branch to be able to include the XDMA DT properties. This branch is stable and
> based on 3.18-rc3 (Cf. http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/304041.html).
> Note that my previous DT pull-request for 3.19 was based on 3.18-rc2.
> So, this is what I did:
> - took a v3.18-rc3 tag
> - merged the at91-3.19-dt branch that you already have in at91/dt (you'd taken the at91-dt tag)
> - merged the topic/at_xdmac from Vinod
> - stacked the new material described above on top of this.
> Tell me if it's okay for you or if I have to arrange things differently.
>
> The content itself is pretty straightforward.
>
I've pulled it into a new next/dt2 branch, so we don't have to coordinate the merging
with Vinod. If he sends the slave-dma tree first, this will be part of the normal
next/dt submission to Linus, otherwise it will come a few days later.
Thanks,
Arnd
prev parent reply other threads:[~2014-11-20 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 16:52 Nicolas Ferre
2014-11-20 12:41 ` Arnd Bergmann [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=201411201341.30112.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alexandre.belloni@free-electrons.com \
--cc=arm@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=olof@lixom.net \
--cc=plagnioj@jcrosoft.com \
--cc=vinod.koul@intel.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
Powered by JetHome