From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Vadym Kochan <vadym.kochan@plvision.eu>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Chris Packham <chris.packham@alliedtelesis.co.nz>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Konstantin Porotchkin <kostap@marvell.com>,
Andrew Lunn <andrew@lunn.ch>,
Robert Marko <robert.marko@sartura.hr>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Elad Nachman <enachman@marvell.com>
Subject: Re: [PATCH v10 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles
Date: Wed, 6 Jul 2022 09:50:52 +0200 [thread overview]
Message-ID: <7f4101ff-7b91-7f22-9de9-06a650143df4@linaro.org> (raw)
In-Reply-To: <20220705190934.6168-2-vadym.kochan@plvision.eu>
On 05/07/2022 21:09, Vadym Kochan wrote:
> From: Chris Packham <chris.packham@alliedtelesis.co.nz>
>
> Describe the compatible properties for the Marvell Alleycat5/5X switches
> with integrated CPUs.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-06 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 19:09 [PATCH v10 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Vadym Kochan
2022-07-05 19:09 ` [PATCH v10 1/3] dt-bindings: marvell: Document the AC5/AC5X compatibles Vadym Kochan
2022-07-06 7:50 ` Krzysztof Kozlowski [this message]
2022-07-05 19:09 ` [PATCH v10 2/3] arm64: dts: marvell: Add Armada 98DX2530 SoC and RD-AC5X board Vadym Kochan
2022-07-05 19:09 ` [PATCH v10 3/3] arm64: marvell: enable the 98DX2530 pinctrl driver Vadym Kochan
2022-07-05 21:02 ` [PATCH v10 0/3] arm64: mvebu: Support for Marvell 98DX2530 (and variants) Chris Packham
2022-07-18 10:48 ` Gregory CLEMENT
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=7f4101ff-7b91-7f22-9de9-06a650143df4@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--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=vadym.kochan@plvision.eu \
--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 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).