From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] at91: Device Tree update for 3.11 #2
Date: Tue, 18 Jun 2013 10:05:30 +0200 [thread overview]
Message-ID: <51C014CA.7040700@atmel.com> (raw)
In-Reply-To: <CAOesGMjHTSB3y3+TxLqM=s06jg8Qx8XnEeW9c2dDcWnneZPVXA@mail.gmail.com>
On 17/06/2013 18:56, Olof Johansson :
> On Mon, Jun 17, 2013 at 1:34 AM, Ferre, Nicolas <Nicolas.FERRE@atmel.com> wrote:
>>
>>> On Sat, Jun 15, 2013 at 12:47:47AM +0200, Nicolas Ferre wrote:
>>>> Arnd, Olof,
>>>>
>>>> Additional pull-request for AT91 DT patches.
>>>> It contains the remaining part of the USB gadget pull-request that I sent you
>>>> last week. After having split it, here is the DT part.
>>>> It also contains the update of DMA bindings: it is the AT91 part the should go
>>>> through arm-soc. I have included the patch (ARM: at91: dt: add header to define
>>>> at_hdmac configuration) so that we avoid build errors whichever git tree
>>>> (slave-dma or arm-soc) is merged first.
>>>> A SPI DT patch for at91sam9x5 is also added.
>>>>
>>>> Thanks, best regards,
>>>>
>>>> The following changes since commit 028633c238f91dc113520a7ad25d37b2ba9068af:
>>>>
>>>> ARM: at91/dt: add pinctrl definition for at91 tc blocks (2013-05-31 22:40:37 +0200)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://github.com/at91linux/linux-at91.git tags/at91-dt
>>>
>>> Pulled, thanks.
>>
>> Hi,
>>
>> I do not see it appearing in arm-soc/at91/dt branch even though is it present in arm-soc/for-next: is it normal?
>
> I had missed to push that (and the driver branch) up. They are there
> now, as at91/dt2 and at91/drivers. Fixed the bad branch name in
> arm-soc-for-next-contents.txt as well.
Nice, thanks.
Bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>, "balbi@ti.com" <balbi@ti.com>,
"richard.genoud@gmail.com" <richard.genoud@gmail.com>,
"Shen, Voice" <Voice.Shen@atmel.com>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"Linux Kernel list" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
"Desroches, Ludovic" <Ludovic.Desroches@atmel.com>
Subject: Re: RE : [GIT PULL] at91: Device Tree update for 3.11 #2
Date: Tue, 18 Jun 2013 10:05:30 +0200 [thread overview]
Message-ID: <51C014CA.7040700@atmel.com> (raw)
In-Reply-To: <CAOesGMjHTSB3y3+TxLqM=s06jg8Qx8XnEeW9c2dDcWnneZPVXA@mail.gmail.com>
On 17/06/2013 18:56, Olof Johansson :
> On Mon, Jun 17, 2013 at 1:34 AM, Ferre, Nicolas <Nicolas.FERRE@atmel.com> wrote:
>>
>>> On Sat, Jun 15, 2013 at 12:47:47AM +0200, Nicolas Ferre wrote:
>>>> Arnd, Olof,
>>>>
>>>> Additional pull-request for AT91 DT patches.
>>>> It contains the remaining part of the USB gadget pull-request that I sent you
>>>> last week. After having split it, here is the DT part.
>>>> It also contains the update of DMA bindings: it is the AT91 part the should go
>>>> through arm-soc. I have included the patch (ARM: at91: dt: add header to define
>>>> at_hdmac configuration) so that we avoid build errors whichever git tree
>>>> (slave-dma or arm-soc) is merged first.
>>>> A SPI DT patch for at91sam9x5 is also added.
>>>>
>>>> Thanks, best regards,
>>>>
>>>> The following changes since commit 028633c238f91dc113520a7ad25d37b2ba9068af:
>>>>
>>>> ARM: at91/dt: add pinctrl definition for at91 tc blocks (2013-05-31 22:40:37 +0200)
>>>>
>>>> are available in the git repository at:
>>>>
>>>> git://github.com/at91linux/linux-at91.git tags/at91-dt
>>>
>>> Pulled, thanks.
>>
>> Hi,
>>
>> I do not see it appearing in arm-soc/at91/dt branch even though is it present in arm-soc/for-next: is it normal?
>
> I had missed to push that (and the driver branch) up. They are there
> now, as at91/dt2 and at91/drivers. Fixed the bad branch name in
> arm-soc-for-next-contents.txt as well.
Nice, thanks.
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-06-18 8:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 8:34 [GIT PULL] at91: USBA DT support for 3.11 Jean-Christophe PLAGNIOL-VILLARD
2013-06-01 4:55 ` Olof Johansson
2013-06-03 17:05 ` [GIT PULL v2] at91: USBA DT support / drivers update for 3.11 #1 Nicolas Ferre
2013-06-03 17:05 ` Nicolas Ferre
2013-06-03 17:10 ` Nicolas Ferre
2013-06-03 17:10 ` Nicolas Ferre
2013-06-11 23:48 ` Olof Johansson
2013-06-11 23:48 ` Olof Johansson
2013-06-14 21:46 ` Nicolas Ferre
2013-06-14 21:46 ` Nicolas Ferre
2013-06-14 22:02 ` [GIT PULL v3] " Nicolas Ferre
2013-06-14 22:02 ` Nicolas Ferre
2013-06-15 2:03 ` Olof Johansson
2013-06-15 2:03 ` Olof Johansson
2013-06-17 9:05 ` Ferre, Nicolas
2013-06-17 9:05 ` RE : " Ferre, Nicolas
2013-06-14 22:47 ` [GIT PULL] at91: Device Tree update for 3.11 #2 Nicolas Ferre
2013-06-14 22:47 ` Nicolas Ferre
2013-06-15 1:52 ` Olof Johansson
2013-06-15 1:52 ` Olof Johansson
2013-06-17 8:34 ` Ferre, Nicolas
2013-06-17 8:34 ` RE : " Ferre, Nicolas
2013-06-17 16:56 ` Olof Johansson
2013-06-17 16:56 ` RE : " Olof Johansson
2013-06-18 8:05 ` Nicolas Ferre [this message]
2013-06-18 8:05 ` Nicolas Ferre
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=51C014CA.7040700@atmel.com \
--to=nicolas.ferre@atmel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.