From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tony Dinh <mibodhi@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] ARM: dts: mvebu: Add device tree binding for Marvell Armada 38x
Date: Wed, 12 Apr 2023 09:13:56 +0200 [thread overview]
Message-ID: <77cadd45-0b15-af1a-9eab-ebe0b3241473@linaro.org> (raw)
In-Reply-To: <20230412025737.20280-2-mibodhi@gmail.com>
On 12/04/2023 04:57, Tony Dinh wrote:
> Add device tree binding for Marvell Armada 38x.
>
> Signed-off-by: Tony Dinh <mibodhi@gmail.com>
Use subject prefixes matching the subsystem (which you can get for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching).
This is not DTS. These are bindings.
> ---
>
> Changes in v2:
> - Add marvell,38x.yaml. For now, add this binding to the Marvell
> directory to keep it consistent with other Marvell yaml files.
> At a later date and a separate patch, consolidate the Marvell
> yaml files into marvell.yaml.
>
> .../bindings/arm/marvell/armada-38x.yaml | 27 +++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml
marvell,armada-38x.yaml
Or just squash it with existing armada bindings... Keeping one binding
per one SoC group is a bit a lot.
>
> diff --git a/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml b/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml
> new file mode 100644
> index 000000000000..096bd46d932a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/marvell/armada-38x.yaml
> @@ -0,0 +1,27 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/marvell/marvell,38x.yaml#
Does not look like you tested the bindings. Please run `make
dt_binding_check` (see
Documentation/devicetree/bindings/writing-schema.rst for instructions).
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-04-12 7:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 2:57 [PATCH v2 0/2] Add support for Thecus N2350 board Tony Dinh
2023-04-12 2:57 ` [PATCH v2 1/2] ARM: dts: mvebu: Add device tree binding for Marvell Armada 38x Tony Dinh
2023-04-12 7:13 ` Krzysztof Kozlowski [this message]
2023-04-12 12:36 ` Rob Herring
2023-04-12 19:05 ` Tony Dinh
2023-04-13 7:51 ` Krzysztof Kozlowski
2023-04-13 19:12 ` Tony Dinh
2023-05-01 22:46 ` Tony Dinh
2023-05-02 6:54 ` Krzysztof Kozlowski
2023-04-12 2:57 ` [PATCH v2 2/2] ARM: dts: mvebu: add Thecus N2350 board DTS Tony Dinh
2023-04-12 12:24 ` Andrew Lunn
2023-04-12 18:50 ` Tony Dinh
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=77cadd45-0b15-af1a-9eab-ebe0b3241473@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mibodhi@gmail.com \
--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
all inboxes | Powered by JetHome®