From: Baruch Siach <baruch@tkos.co.il>
To: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz>
Cc: andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com, robh+dt@kernel.org,
devicetree@vger.kernel.org, chris.packham@alliedtelesis.co.nz,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: mvebu: Add device tree for ATL-x530 Board
Date: Mon, 30 Nov 2020 06:55:13 +0200 [thread overview]
Message-ID: <87h7p7e95a.fsf@tarshish> (raw)
In-Reply-To: <20201130025410.6669-1-aryan.srivastava@alliedtelesis.co.nz>
Hi Aryan,
[ Dropped Jason's bouncing address from Cc ]
On Mon, Nov 30 2020, Aryan Srivastava wrote:
> Add device tree file for x530 board. This has an Armada 385 SoC. Has
> NAND-flash for user storage and SPI for booting. Covers majority of x530
> and GS980MX variants.
>
> Signed-off-by: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz>
> Reviewed-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> arch/arm/boot/dts/armada-385-atl-x530.dts | 235 ++++++++++++++++++++++
You need to add this .dts to Makefile for it to build with the rest.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
WARNING: multiple messages have this Message-ID (diff)
From: Baruch Siach <baruch@tkos.co.il>
To: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz>
Cc: andrew@lunn.ch, devicetree@vger.kernel.org,
gregory.clement@bootlin.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, chris.packham@alliedtelesis.co.nz,
linux-arm-kernel@lists.infradead.org,
sebastian.hesselbarth@gmail.com
Subject: Re: [PATCH] ARM: dts: mvebu: Add device tree for ATL-x530 Board
Date: Mon, 30 Nov 2020 06:55:13 +0200 [thread overview]
Message-ID: <87h7p7e95a.fsf@tarshish> (raw)
In-Reply-To: <20201130025410.6669-1-aryan.srivastava@alliedtelesis.co.nz>
Hi Aryan,
[ Dropped Jason's bouncing address from Cc ]
On Mon, Nov 30 2020, Aryan Srivastava wrote:
> Add device tree file for x530 board. This has an Armada 385 SoC. Has
> NAND-flash for user storage and SPI for booting. Covers majority of x530
> and GS980MX variants.
>
> Signed-off-by: Aryan Srivastava <aryan.srivastava@alliedtelesis.co.nz>
> Reviewed-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> arch/arm/boot/dts/armada-385-atl-x530.dts | 235 ++++++++++++++++++++++
You need to add this .dts to Makefile for it to build with the rest.
baruch
--
~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-30 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 2:54 [PATCH] ARM: dts: mvebu: Add device tree for ATL-x530 Board Aryan Srivastava
2020-11-30 2:54 ` Aryan Srivastava
2020-11-30 4:55 ` Baruch Siach [this message]
2020-11-30 4:55 ` Baruch Siach
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=87h7p7e95a.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=andrew@lunn.ch \
--cc=aryan.srivastava@alliedtelesis.co.nz \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.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 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.