public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v6 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards
Date: Tue, 31 Jan 2017 12:05:59 +0100	[thread overview]
Message-ID: <877f5b1obs.fsf@free-electrons.com> (raw)
In-Reply-To: <25e75991d565411fa9bccb6d2f71babf@svr-chch-ex1.atlnz.lc> (Chris Packham's message of "Mon, 30 Jan 2017 22:02:38 +0000")

Hi Chris,
 
 On lun., janv. 30 2017, Chris Packham <Chris.Packham@alliedtelesis•co.nz> wrote:

> Hi Gregory,
>
> On 31/01/17 03:29, Gregory CLEMENT wrote:
>> Hi Chris,
>>
>>  On lun., janv. 30 2017, Chris Packham <chris.packham@alliedtelesis•co.nz> wrote:
>>
>>> These boards are Marvell's evaluation boards for the 98DX4251 and
>>> 98DX3336 SoCs.
>>>
>>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis•co.nz>
>>
>> Applied on mvebu/dt
>>
>
> I just noticed that I hadn't updated arch/arm/boot/dts/Makefile. The way 
> I've been building things (explicitly running 'make 
> armada-xp-db-xc3-24g4xg.dtb') it hasn't mattered to me but I'm wondering 
> if I should have?

As I didn't make a Pull request yet, I was able to fix it on the fly.

Gregory

>
>>> ---
>>>
>>> Notes:
>>>     Changes in v5:
>>>     - update license text
>>>     - use node labels
>>>     Changes in v6:
>>>     - Rename dts files to include 'armada-xp-' prefix
>>>
>>>  arch/arm/boot/dts/armada-xp-db-dxbc2.dts      | 151 ++++++++++++++++++++++++++
>>>  arch/arm/boot/dts/armada-xp-db-xc3-24g4xg.dts | 142 ++++++++++++++++++++++++
>>>  2 files changed, 293 insertions(+)
>>>  create mode 100644 arch/arm/boot/dts/armada-xp-db-dxbc2.dts
>>>  create mode 100644 arch/arm/boot/dts/armada-xp-db-xc3-24g4xg.dts
>>>
>

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2017-01-31 11:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 23:20 [PATCHv5 0/5] Support for Marvell switches with integrated CPUs Chris Packham
2017-01-29 23:20 ` [PATCH v6 1/5] clk: mvebu: support for 98DX3236 SoC Chris Packham
2017-01-29 23:20 ` [PATCH v6 2/5] arm: mvebu: support for SMP on 98DX3336 SoC Chris Packham
2017-01-30 14:26   ` Gregory CLEMENT
2017-01-29 23:20 ` [PATCH v6 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC Chris Packham
2017-01-30 13:58   ` Linus Walleij
2017-01-29 23:20 ` [PATCH v6 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs Chris Packham
2017-01-30 14:29   ` Gregory CLEMENT
2017-01-29 23:20 ` [PATCH v6 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards Chris Packham
2017-01-30 14:29   ` Gregory CLEMENT
2017-01-30 22:02     ` Chris Packham
2017-01-31 11:05       ` Gregory CLEMENT [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=877f5b1obs.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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