From: "Sugaya, Taichi" <sugaya.taichi@socionext.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
Shinji Kanematsu <kanematsu.shinji@socionext.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
soc@kernel.org, Takao Orito <orito.takao@socionext.com>,
Kazuhiro Kasai <kasai.kazuhiro@socionext.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/9] dt-bindings: Add documentation for Milbeaut SoCs
Date: Thu, 21 Feb 2019 09:37:55 +0900 [thread overview]
Message-ID: <f31aa3e4-9f86-124f-6636-d2c2b4763cca@socionext.com> (raw)
In-Reply-To: <CAL_JsqK-8iBaF92GpXdoZwBEaT_mQAjO_4URR9iPJqAiy=YW=w@mail.gmail.com>
Hi,
On 2019/02/20 22:33, Rob Herring wrote:
> On Wed, Feb 20, 2019 at 1:43 AM Sugaya Taichi
> <sugaya.taichi@socionext.com> wrote:
>>
>> This adds a DT binding documentation for the M10V and its evaluation
>> board.
>>
>> Signed-off-by: Sugaya Taichi <sugaya.taichi@socionext.com>
>> ---
>> .../bindings/arm/socionext/milbeaut.yaml | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/arm/socionext/milbeaut.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/arm/socionext/milbeaut.yaml b/Documentation/devicetree/bindings/arm/socionext/milbeaut.yaml
>> new file mode 100644
>> index 0000000..522396f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/socionext/milbeaut.yaml
>> @@ -0,0 +1,22 @@
>> +# SPDX-License-Identifier: GPL-2.0
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/arm/milbeaut.yaml#
>> +$schema: http://devicetree.org/meta-schemas/milbeaut.yaml#
>
> This line is wrong. All DT schema should be:
> http://devicetree.org/meta-schemas/core.yaml#
>
Ah, OK. Fix it soon.
Thanks,
Sugaya Taichi
>> +
>> +title: Milbeaut platforms device tree bindings
>> +
>> +maintainers:
>> + - Taichi Sugaya <sugaya.taichi@socionext.com>
>> + - Takao Orito <orito.takao@socionext.com>
>> +
>> +properties:
>> + $nodename:
>> + const: '/'
>> + compatible:
>> + oneOf:
>> + - items:
>> + - enum:
>> + - socionext,milbeaut-m10v-evb
>> + - const: socionext,sc2000a
>> +...
>> --
>> 1.9.1
>>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-21 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 7:43 [PATCH v3 3/9] dt-bindings: Add documentation for Milbeaut SoCs Sugaya Taichi
2019-02-20 13:33 ` Rob Herring
2019-02-21 0:37 ` Sugaya, Taichi [this message]
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=f31aa3e4-9f86-124f-6636-d2c2b4763cca@socionext.com \
--to=sugaya.taichi@socionext.com \
--cc=devicetree@vger.kernel.org \
--cc=jaswinder.singh@linaro.org \
--cc=kanematsu.shinji@socionext.com \
--cc=kasai.kazuhiro@socionext.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masami.hiramatsu@linaro.org \
--cc=orito.takao@socionext.com \
--cc=robh+dt@kernel.org \
--cc=soc@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).