From: Rob Herring <robh@kernel.org>
To: peng.fan@nxp.com
Cc: shawnguo@kernel.org, s.hauer@pengutronix.de, robh+dt@kernel.org,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
Anson.Huang@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V3 1/4] dt-bindings: fsl: add i.MX7ULP PMC binding doc
Date: Wed, 18 Mar 2020 16:13:04 -0600 [thread overview]
Message-ID: <20200318221304.GA28525@bogus> (raw)
In-Reply-To: <1584348944-19633-2-git-send-email-peng.fan@nxp.com>
On Mon, 16 Mar 2020 16:55:41 +0800, peng.fan@nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Add i.MX7ULP Power Management Controller binding doc
> pmc0 is used by M4, pmc1 is used by A7, they have different
> register name and usage.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> .../bindings/arm/freescale/imx7ulp_pmc.yaml | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/freescale/imx7ulp_pmc.yaml
>
My bot found errors running 'make dt_binding_check' on your patch:
Documentation/devicetree/bindings/arm/freescale/imx7ulp_pmc.yaml: $id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/arm/freescale/imx7ulp_pmc.yaml#
See https://patchwork.ozlabs.org/patch/1255335
Please check and re-submit.
next prev parent reply other threads:[~2020-03-18 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 8:55 [PATCH V3 0/4] ARM: imx7ulp: support HSRUN mode peng.fan
2020-03-16 8:55 ` [PATCH V3 1/4] dt-bindings: fsl: add i.MX7ULP PMC binding doc peng.fan
2020-03-18 22:13 ` Rob Herring [this message]
2020-03-16 8:55 ` [PATCH V3 2/4] ARM: dts: imx7ulp: add pmc node peng.fan
2020-03-16 8:55 ` [PATCH V3 3/4] ARM: imx: imx7ulp: support HSRUN mode peng.fan
2020-03-16 8:55 ` [PATCH V3 4/4] ARM: imx: cpuidle-imx7ulp: Stop mode disallowed when HSRUN peng.fan
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=20200318221304.GA28525@bogus \
--to=robh@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).