From: Rob Herring <robh@kernel.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: Cyril.Jean@microchip.com, Ivan.Griffin@microchip.com,
Rob Herring <robh+dt@kernel.org>,
Alistair Francis <alistair.francis@wdc.com>,
linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@dabbelt.com>,
Conor.Dooley@microchip.com, linux-kernel@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
Anup Patel <anup.patel@wdc.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Albert Ou <aou@eecs.berkeley.edu>,
devicetree@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/4] dt-bindings: riscv: microchip: Add YAML documentation for the PolarFire SoC
Date: Mon, 16 Nov 2020 09:01:29 -0600 [thread overview]
Message-ID: <20201116150129.GA1643948@bogus> (raw)
In-Reply-To: <20201113202550.3693323-3-atish.patra@wdc.com>
On Fri, 13 Nov 2020 12:25:48 -0800, Atish Patra wrote:
> Add YAML DT binding documentation for the Microchip PolarFire SoC.
> It is documented at:
>
> https://www.microsemi.com/products/fpga-soc/polarfire-soc-icicle-quick-start-guide
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> ---
> .../devicetree/bindings/riscv/microchip.yaml | 27 +++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/riscv/microchip.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
./Documentation/devicetree/bindings/riscv/microchip.yaml: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/riscv/microchip.yaml#
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/riscv/sifive.yaml: duplicate '$id' value 'http://devicetree.org/schemas/riscv/sifive.yaml#'
See https://patchwork.ozlabs.org/patch/1400088
The base for the patch is generally the last rc1. Any dependencies
should be noted.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit.
next prev parent reply other threads:[~2020-11-16 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 20:25 [RFC PATCH v2 0/4] Add Microchip PolarFire Soc Support Atish Patra
2020-11-13 20:25 ` [RFC PATCH v2 1/4] RISC-V: Add Microchip PolarFire SoC kconfig option Atish Patra
2020-11-13 20:25 ` [RFC PATCH v2 2/4] dt-bindings: riscv: microchip: Add YAML documentation for the PolarFire SoC Atish Patra
2020-11-16 15:01 ` Rob Herring [this message]
2020-11-16 16:08 ` Atish Patra
2020-11-13 20:25 ` [RFC PATCH v2 3/4] RISC-V: Initial DTS for Microchip ICICLE board Atish Patra
2020-11-17 2:14 ` Bin Meng
2020-11-17 6:07 ` Atish Patra
2020-11-21 8:52 ` Anup Patel
[not found] ` <DM6PR11MB4267B9C027125D8EE8B114E196F30@DM6PR11MB4267.namprd11.prod.outlook.com>
2020-12-02 18:49 ` Atish Patra
2020-11-13 20:25 ` [RFC PATCH v2 4/4] RISC-V: Enable Microchip PolarFire ICICLE SoC Atish Patra
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=20201116150129.GA1643948@bogus \
--to=robh@kernel.org \
--cc=Conor.Dooley@microchip.com \
--cc=Cyril.Jean@microchip.com \
--cc=Ivan.Griffin@microchip.com \
--cc=alistair.francis@wdc.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@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).