From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: at91/DT: enable SPI for more SoCs
Date: Wed, 26 Jun 2013 11:05:34 +0200 [thread overview]
Message-ID: <51CAAEDE.7050906@atmel.com> (raw)
In-Reply-To: <B256D81BAE5131468A838E5D7A243641687DF77C@penmbx01>
On 26/06/2013 03:59, Yang, Wenyou :
>
>
>> -----Original Message-----
>> From: Nicolas Ferre [mailto:nicolas.ferre at atmel.com]
>> Sent: 2013?6?24? 18:35
>> To: Jean-Christophe PLAGNIOL-VILLARD; Desroches, Ludovic; Yang, Wenyou;
>> Shen, Voice; Wu, Josh
>> Cc: linux-arm-kernel at lists.infradead.org; linux-kernel at vger.kernel.org; Ferre,
>> Nicolas
>> Subject: [PATCH 0/3] ARM: at91/DT: enable SPI for more SoCs
>>
>> This little series is for enabling the support of SPI on at91sam9n12 and
>> sama5d3 families.
>>
>> Nicolas Ferre (3):
>> ARM: at91/DT: fix SPI compatibility string
>> ARM: at91/DT: sama5d3: add SPI DMA client infos
>> ARM: at91/DT: at91sam9n12: add SPI DMA client infos
>>
>> arch/arm/boot/dts/at91sam9n12.dtsi | 6 ++++++
>> arch/arm/boot/dts/sama5d3.dtsi | 10 ++++++++--
>> 2 files changed, 14 insertions(+), 2 deletions(-)
>>
>> --
>> 1.8.2.2
>
> Tested on sama5d34ek, Linux-next: next-20130624
>
> Tested by Wenyou Yang <wenyou.yang@atmel.com>
Thanks for having testing: series is stacked on at91-3.11-dt now.
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2013-06-26 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 10:35 [PATCH 0/3] ARM: at91/DT: enable SPI for more SoCs Nicolas Ferre
2013-06-24 10:35 ` [PATCH 1/3] ARM: at91/DT: fix SPI compatibility string Nicolas Ferre
2013-06-24 10:35 ` [PATCH 2/3] ARM: at91/DT: sama5d3: add SPI DMA client infos Nicolas Ferre
2013-06-24 10:35 ` [PATCH 3/3] ARM: at91/DT: at91sam9n12: " Nicolas Ferre
2013-06-26 1:59 ` [PATCH 0/3] ARM: at91/DT: enable SPI for more SoCs Yang, Wenyou
2013-06-26 9:05 ` Nicolas Ferre [this message]
2013-08-21 11:28 ` Jean-Christophe PLAGNIOL-VILLARD
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=51CAAEDE.7050906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).