From: Rob Herring <robh@kernel.org>
To: "Jimmy Chen (陳永達)" <jimmy.chen@moxa.com>
Cc: "krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Add an entry for MOXA platform board
Date: Wed, 6 Jul 2022 10:15:17 -0600 [thread overview]
Message-ID: <20220706161517.GA140402-robh@kernel.org> (raw)
In-Reply-To: <SEYPR01MB4272F28F81FB51152496D9CBFA809@SEYPR01MB4272.apcprd01.prod.exchangelabs.com>
On Wed, Jul 06, 2022 at 07:22:23AM +0000, Jimmy Chen (陳永達) wrote:
> UC-8220 & UC-8210 hardware compatibility model
>
> Signed-off-by: Jimmy Chen <jimmy.chen@moxa.com>
> ---
> .../devicetree/bindings/arm/moxa.yaml | 21 +++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/moxa.yaml
What's the relationship to moxart.yaml?
>
> diff --git a/Documentation/devicetree/bindings/arm/moxa.yaml b/Documentation/devicetree/bindings/arm/moxa.yaml
> new file mode 100644
> index 000000000000..73f4bf883b06
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/moxa.yaml
> @@ -0,0 +1,21 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/moxa.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: MOXA platform device tree bindings
> +
> +maintainers:
> + - Jimmy Chen <jimmy.chen@moxa.com>
> +
> +properties:
> + compatible:
> + description: UC-82XX-LX embedded computer
> + items:
> + - const: moxa,uc-8210
> + - const: moxa,uc-8220
> +
> +additionalProperties: true
> +...
> +
> --
> 2.20.1
>
next prev parent reply other threads:[~2022-07-06 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 7:22 [PATCH 2/2] Add an entry for MOXA platform board Jimmy Chen (陳永達)
2022-07-06 7:25 ` Krzysztof Kozlowski
2022-07-06 16:15 ` Rob Herring [this message]
2022-07-07 2:09 ` Jimmy Chen (陳永達)
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=20220706161517.GA140402-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jimmy.chen@moxa.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.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).