All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: at91: add Acme Systems Aria G25 board
Date: Thu, 4 Apr 2013 17:29:56 +0200	[thread overview]
Message-ID: <515D9C74.5050207@atmel.com> (raw)
In-Reply-To: <515C7E94.6030702@interlog.com>

On 04/03/2013 09:10 PM, Douglas Gilbert :
> On 13-04-02 02:48 PM, Olof Johansson wrote:
>> Hi,
>>
>> I just saw this since it came in through a pull request
>>
>> On Tue, Mar 26, 2013 at 4:39 AM, Nicolas Ferre
>> <nicolas.ferre@atmel.com> wrote:
>>> From: Douglas Gilbert <dgilbert@interlog.com>
>>>
>>> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> ---
>>>   arch/arm/boot/dts/ariag25.dts | 175
>>> ++++++++++++++++++++++++++++++++++++++++++
>>>   1 file changed, 175 insertions(+)
>>>   create mode 100644 arch/arm/boot/dts/ariag25.dts
>>>
>>> diff --git a/arch/arm/boot/dts/ariag25.dts
>>> b/arch/arm/boot/dts/ariag25.dts
>>> new file mode 100644
>>> index 0000000..b43266f
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/ariag25.dts
>>
>> Please prefix the boards with the platform. Most other SoCs already do
>> this, and I see now that some at91 boards haven't been prefixed in the
>> past, but it's a good idea to not add more of them.
>>
>> So, at91-ariag25.dts is a good name in this case.
> 
> That is fine with me. I have changed my working DT
> config file to at91-ariag25.dts and will push that
> out to Robert Nelson soon.
> 
> Also I'm working on a DT version of an existing Acme
> product called the FoxG20 which is based on the
> AT91SAM9G20 SoC. It already has non-DT support inside
> the mainline kernel. I am using at91-foxg20.dts for
> its DT config file.

Yep! Works for me.

Bye,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: <dgilbert@interlog.com>
Cc: Olof Johansson <olof@lixom.net>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	Ludovic Desroches <ludovic.desroches@atmel.com>,
	<tanzilli@acmesystems.it>, <Robert.Nelson@digikey.com>
Subject: Re: [PATCH v2] ARM: at91: add Acme Systems Aria G25 board
Date: Thu, 4 Apr 2013 17:29:56 +0200	[thread overview]
Message-ID: <515D9C74.5050207@atmel.com> (raw)
In-Reply-To: <515C7E94.6030702@interlog.com>

On 04/03/2013 09:10 PM, Douglas Gilbert :
> On 13-04-02 02:48 PM, Olof Johansson wrote:
>> Hi,
>>
>> I just saw this since it came in through a pull request
>>
>> On Tue, Mar 26, 2013 at 4:39 AM, Nicolas Ferre
>> <nicolas.ferre@atmel.com> wrote:
>>> From: Douglas Gilbert <dgilbert@interlog.com>
>>>
>>> Signed-off-by: Douglas Gilbert <dgilbert@interlog.com>
>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>>> ---
>>>   arch/arm/boot/dts/ariag25.dts | 175
>>> ++++++++++++++++++++++++++++++++++++++++++
>>>   1 file changed, 175 insertions(+)
>>>   create mode 100644 arch/arm/boot/dts/ariag25.dts
>>>
>>> diff --git a/arch/arm/boot/dts/ariag25.dts
>>> b/arch/arm/boot/dts/ariag25.dts
>>> new file mode 100644
>>> index 0000000..b43266f
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/ariag25.dts
>>
>> Please prefix the boards with the platform. Most other SoCs already do
>> this, and I see now that some at91 boards haven't been prefixed in the
>> past, but it's a good idea to not add more of them.
>>
>> So, at91-ariag25.dts is a good name in this case.
> 
> That is fine with me. I have changed my working DT
> config file to at91-ariag25.dts and will push that
> out to Robert Nelson soon.
> 
> Also I'm working on a DT version of an existing Acme
> product called the FoxG20 which is based on the
> AT91SAM9G20 SoC. It already has non-DT support inside
> the mainline kernel. I am using at91-foxg20.dts for
> its DT config file.

Yep! Works for me.

Bye,
-- 
Nicolas Ferre

  reply	other threads:[~2013-04-04 15:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  8:49 [PATCH] ARM: at91: add Acme Systems Aria G25 board Nicolas Ferre
2013-03-25  8:49 ` Nicolas Ferre
2013-03-25 12:22 ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 12:22   ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 12:33   ` Douglas Gilbert
2013-03-25 12:33     ` Douglas Gilbert
2013-03-25 13:48   ` Douglas Gilbert
2013-03-25 13:48     ` Douglas Gilbert
2013-03-25 14:10     ` Nicolas Ferre
2013-03-25 14:10       ` Nicolas Ferre
2013-03-25 14:31     ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 14:31       ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 15:23       ` Douglas Gilbert
2013-03-25 15:23         ` Douglas Gilbert
2013-03-25 17:04         ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 17:04           ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 14:11   ` Nicolas Ferre
2013-03-25 14:11     ` Nicolas Ferre
2013-03-25 14:34     ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-25 14:34       ` Jean-Christophe PLAGNIOL-VILLARD
2013-03-26 11:39 ` [PATCH v2] " Nicolas Ferre
2013-03-26 11:39   ` Nicolas Ferre
2013-04-02 18:48   ` Olof Johansson
2013-04-02 18:48     ` Olof Johansson
2013-04-03 19:10     ` Douglas Gilbert
2013-04-03 19:10       ` Douglas Gilbert
2013-04-04 15:29       ` Nicolas Ferre [this message]
2013-04-04 15:29         ` 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=515D9C74.5050207@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.