From: Andrew Lunn <andrew@lunn.ch>
To: "Pali Rohár" <pali@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: marvell: Update Armada 37xx platform bindings
Date: Tue, 9 Aug 2022 16:58:36 +0200 [thread overview]
Message-ID: <YvJ2HKqMTTyWiNth@lunn.ch> (raw)
In-Reply-To: <20220809131252.z3mbmiz4duxwlauw@pali>
On Tue, Aug 09, 2022 at 03:12:52PM +0200, Pali Rohár wrote:
> + Andrew, Gregory, Sebastian
>
> please comment on this
Krzysztof said:
> The change is an ABI break, which looks reasonable, but still
> platform maintainer should comment on it. Especially on the aspect
> why the marvell,armada3710 fallback was chosen at the first place.
I was not involved in the armada37xx enablement. I have no idea why
marvell,armada3710 fallback was chosen.
Gregory might know, he is the author of this file.
It does however seem reasonable. And a grep does suggest this
compatible is purely cosmetic, it is not matched on anywhere.
Andrew
next prev parent reply other threads:[~2022-08-09 14:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 20:01 [PATCH] dt-bindings: marvell: Update Armada 37xx platform bindings Pali Rohár
2022-07-18 20:57 ` Rob Herring
2022-08-08 20:23 ` Pali Rohár
2022-08-09 5:58 ` Krzysztof Kozlowski
2022-08-09 13:13 ` Pali Rohár
2022-08-09 15:46 ` Krzysztof Kozlowski
2022-08-09 15:48 ` Pali Rohár
2022-09-24 13:50 ` Krzysztof Kozlowski
2022-09-24 14:30 ` Pali Rohár
2022-09-24 16:53 ` Krzysztof Kozlowski
2022-08-09 13:12 ` Pali Rohár
2022-08-09 14:58 ` Andrew Lunn [this message]
2023-02-01 8:27 ` Gregory CLEMENT
2022-09-24 12:06 ` Pali Rohár
2022-10-09 11:56 ` Pali Rohár
2022-11-01 22:43 ` Pali Rohár
2022-11-28 18:18 ` Pali Rohár
2022-12-16 18:20 ` Pali Rohár
2023-01-22 11:29 ` Pali Rohár
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=YvJ2HKqMTTyWiNth@lunn.ch \
--to=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@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 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).