From: Vadym Kochan <vadym.kochan@plvision.eu>
To: catalin.marinas@arm.com, will@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, andrew@lunn.ch,
gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com,
kostap@marvell.com, robert.marko@sartura.hr
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Elad Nachman <enachman@marvell.com>
Subject: Re: [PATCH v5 1/2] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
Date: Wed, 11 May 2022 19:10:03 +0300 [thread overview]
Message-ID: <20220511161003.GE10145@plvision.eu> (raw)
In-Reply-To: <20220504044624.951841-1-chris.packham@alliedtelesis.co.nz>
Hi Chris,
> arch/arm64/boot/dts/marvell/Makefile | 1 +
> .../boot/dts/marvell/armada-98dx2530.dtsi | 310 ++++++++++++++++++
> arch/arm64/boot/dts/marvell/rd-ac5x.dts | 90 +++++
> 3 files changed, 401 insertions(+)
Marvell is going to start the upstreaming of AC5X boards support, we have also patches with similar .dts(i) files
but with different naming:
ac5.dtsi
ac5_rd.dts
ac5_db.dts
ac5x_db.dts
What do you think about to use these naming scheme ?
Regards,
Vadym Kochan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Vadym Kochan <vadym.kochan@plvision.eu>
To: catalin.marinas@arm.com, will@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, andrew@lunn.ch,
gregory.clement@bootlin.com, sebastian.hesselbarth@gmail.com,
kostap@marvell.com, robert.marko@sartura.hr
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Elad Nachman <enachman@marvell.com>
Subject: Re: [PATCH v5 1/2] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board
Date: Wed, 11 May 2022 19:10:03 +0300 [thread overview]
Message-ID: <20220511161003.GE10145@plvision.eu> (raw)
In-Reply-To: <20220504044624.951841-1-chris.packham@alliedtelesis.co.nz>
Hi Chris,
> arch/arm64/boot/dts/marvell/Makefile | 1 +
> .../boot/dts/marvell/armada-98dx2530.dtsi | 310 ++++++++++++++++++
> arch/arm64/boot/dts/marvell/rd-ac5x.dts | 90 +++++
> 3 files changed, 401 insertions(+)
Marvell is going to start the upstreaming of AC5X boards support, we have also patches with similar .dts(i) files
but with different naming:
ac5.dtsi
ac5_rd.dts
ac5_db.dts
ac5x_db.dts
What do you think about to use these naming scheme ?
Regards,
Vadym Kochan
next prev parent reply other threads:[~2022-05-11 16:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 4:46 [PATCH v5 0/2] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Chris Packham
2022-05-04 4:46 ` Chris Packham
2022-05-04 4:46 ` [PATCH v5 1/2] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Chris Packham
2022-05-04 4:46 ` Chris Packham
2022-05-05 9:19 ` Krzysztof Kozlowski
2022-05-05 9:19 ` Krzysztof Kozlowski
2022-05-10 4:14 ` Chris Packham
2022-05-10 4:14 ` Chris Packham
2022-05-10 7:08 ` Krzysztof Kozlowski
2022-05-10 7:08 ` Krzysztof Kozlowski
2022-05-10 12:37 ` Andrew Lunn
2022-05-10 12:37 ` Andrew Lunn
2022-05-10 12:54 ` Krzysztof Kozlowski
2022-05-10 12:54 ` Krzysztof Kozlowski
2022-05-10 21:51 ` Chris Packham
2022-05-10 21:51 ` Chris Packham
2022-05-10 22:00 ` Chris Packham
2022-05-10 22:00 ` Chris Packham
2022-05-04 4:46 ` [PATCH v5 2/2] arm64: marvell: enable the 98DX2530 pinctrl driver Chris Packham
2022-05-04 4:46 ` Chris Packham
2022-05-11 16:10 ` Vadym Kochan [this message]
2022-05-11 16:10 ` [PATCH v5 1/2] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Vadym Kochan
2022-05-11 16:20 ` Andrew Lunn
2022-05-11 16:20 ` Andrew Lunn
2022-05-11 22:59 ` Chris Packham
2022-05-11 22:59 ` Chris Packham
2022-05-12 0:39 ` Andrew Lunn
2022-05-12 0:39 ` Andrew Lunn
2022-05-12 6:57 ` [EXT] " Elad Nachman
2022-05-12 6:57 ` Elad Nachman
2022-05-12 12:47 ` Andrew Lunn
2022-05-12 12:47 ` Andrew Lunn
2022-05-12 21:19 ` Chris Packham
2022-05-12 21:19 ` Chris Packham
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=20220511161003.GE10145@plvision.eu \
--to=vadym.kochan@plvision.eu \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=enachman@marvell.com \
--cc=gregory.clement@bootlin.com \
--cc=kostap@marvell.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=will@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 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.