From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
ulf.hansson@linaro.org, robh+dt@kernel.org, krzk+dt@kernel.org,
andrew@lunn.ch, gregory.clement@bootlin.com,
sebastian.hesselbarth@gmail.com
Cc: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] dt-bindings: mmc: convert orion-sdio to JSON schema
Date: Mon, 18 Apr 2022 13:41:42 +0200 [thread overview]
Message-ID: <09df1d1f-71cf-a24f-2908-8e1630d9c536@linaro.org> (raw)
In-Reply-To: <20220414230603.567049-4-chris.packham@alliedtelesis.co.nz>
On 15/04/2022 01:06, Chris Packham wrote:
> Convert the orion-sdio binding to JSON schema.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> ---
> .../bindings/mmc/marvell,orion-sdio.yaml | 43 +++++++++++++++++++
> .../devicetree/bindings/mmc/orion-sdio.txt | 16 -------
> 2 files changed, 43 insertions(+), 16 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml
> delete mode 100644 Documentation/devicetree/bindings/mmc/orion-sdio.txt
>
> diff --git a/Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml b/Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml
> new file mode 100644
> index 000000000000..4fef53fc78ed
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mmc/marvell,orion-sdio.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mmc/marvell,orion-sdio.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Marvell orion-sdio controller
> +
> +maintainers:
> + - Ulf Hansson <ulf.hansson@linaro.org>
This should be someone having taking care about this hardware, not
subsystem maintainer. If there is no dedicated person for Marvell MMC,
then maybe SoC maintainers?
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-18 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 23:05 [PATCH 0/4] dt-bindings: mmc: Convert orion/dove bindings to JSON schema Chris Packham
2022-04-14 23:06 ` [PATCH 1/4] ARM: dts: mvebu: Update mvsdio node names to match schema Chris Packham
2022-04-14 23:06 ` [PATCH 2/4] ARM: dts: dove: Update sdio-host " Chris Packham
2022-04-14 23:06 ` [PATCH 3/4] dt-bindings: mmc: convert orion-sdio to JSON schema Chris Packham
2022-04-15 14:32 ` Rob Herring
2022-04-20 21:16 ` Rob Herring
2022-04-18 11:41 ` Krzysztof Kozlowski [this message]
2022-04-14 23:06 ` [PATCH 4/4] dt-bindings: mmc: convert sdhci-dove " Chris Packham
2022-04-14 23:33 ` Andrew Lunn
2022-04-18 11:43 ` Krzysztof Kozlowski
2022-04-15 14:32 ` Rob Herring
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=09df1d1f-71cf-a24f-2908-8e1630d9c536@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=ulf.hansson@linaro.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).