devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Araneda <luaraneda@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Michal Simek <michal.simek@xilinx.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Luis Araneda <luaraneda@gmail.com>
Subject: [RFC PATCH 1/5] arm: dts: zynq: Set correct manufacturer for ZedBoard and MicroZed boards
Date: Thu, 28 Jun 2018 01:42:01 -0400	[thread overview]
Message-ID: <20180628054205.17737-2-luaraneda@gmail.com> (raw)
In-Reply-To: <20180628054205.17737-1-luaraneda@gmail.com>

Both boards are made by Avnet, Inc.

Signed-off-by: Luis Araneda <luaraneda@gmail.com>
---
 arch/arm/boot/dts/zynq-microzed.dts | 2 +-
 arch/arm/boot/dts/zynq-zed.dts      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/zynq-microzed.dts b/arch/arm/boot/dts/zynq-microzed.dts
index aa4a0b6de..e40f40a7f 100644
--- a/arch/arm/boot/dts/zynq-microzed.dts
+++ b/arch/arm/boot/dts/zynq-microzed.dts
@@ -8,7 +8,7 @@
 
 / {
 	model = "Zynq MicroZED Development Board";
-	compatible = "xlnx,zynq-microzed", "xlnx,zynq-7000";
+	compatible = "avnet,zynq-microzed", "xlnx,zynq-7000";
 
 	aliases {
 		ethernet0 = &gem0;
diff --git a/arch/arm/boot/dts/zynq-zed.dts b/arch/arm/boot/dts/zynq-zed.dts
index 53c6883ce..98381cc85 100644
--- a/arch/arm/boot/dts/zynq-zed.dts
+++ b/arch/arm/boot/dts/zynq-zed.dts
@@ -8,7 +8,7 @@
 
 / {
 	model = "Zynq Zed Development Board";
-	compatible = "xlnx,zynq-zed", "xlnx,zynq-7000";
+	compatible = "avnet,zynq-zed", "xlnx,zynq-7000";
 
 	aliases {
 		ethernet0 = &gem0;
-- 
2.18.0

  reply	other threads:[~2018-06-28  5:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28  5:42 [RFC PATCH 0/5] arm: dts: zynq: improvements and cleanup Luis Araneda
2018-06-28  5:42 ` Luis Araneda [this message]
2018-06-28  6:36   ` [RFC PATCH 1/5] arm: dts: zynq: Set correct manufacturer for ZedBoard and MicroZed boards Michal Simek
2018-07-03  6:51     ` Luis Araneda
2018-06-28  5:42 ` [RFC PATCH 2/5] dt-bindings: xilinx: Add missing zynq boards Luis Araneda
2018-06-28  6:44   ` Michal Simek
2018-07-03  6:53     ` Luis Araneda
2018-07-03 23:04   ` Rob Herring
2018-07-05 21:10     ` Luis Araneda
2018-06-28  5:42 ` [RFC PATCH 3/5] arm: dts: zynq: correct and improve the model property of dt files Luis Araneda
2018-06-28  6:39   ` Michal Simek
2018-06-28  5:42 ` [RFC PATCH 4/5] arm: dts: zynq: rename board zed to zedboard Luis Araneda
2018-06-28  6:40   ` Michal Simek
2018-07-03  6:56     ` Luis Araneda
2018-06-28  5:42 ` [RFC PATCH 5/5] arm: dts: zynq: remove "zynq" prefix from compatible property Luis Araneda
2018-06-28  6:41   ` Michal Simek
2018-07-03  7:18     ` Luis Araneda
2018-07-03 23:07       ` Rob Herring
2018-07-05 21:12         ` Luis Araneda

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=20180628054205.17737-2-luaraneda@gmail.com \
    --to=luaraneda@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=robh+dt@kernel.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).