From: Jeremy McNicoll <jmcnicol@redhat.com>
To: Jeremy McNicoll <jeremymc@redhat.com>
Cc: linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-mmc@vger.kernel.org,
andy.gross@linaro.org, sboyd@codeaurora.org, robh@kernel.org,
arnd@arndb.de, bjorn.andersson@linaro.org,
riteshh@codeaurora.org, git@kchr.de, ulf.hansson@linaro.org,
jszhang@marvell.com
Subject: Re: [PATCH V2 4/4] dts: doc: rename rpm_requests to respect DT naming conventions
Date: Mon, 23 Jan 2017 02:39:47 -0800 [thread overview]
Message-ID: <20170123103947.GA22659@mini-rhel.redhat.com> (raw)
In-Reply-To: <1484614729-26751-5-git-send-email-jeremymc@redhat.com>
On Mon, Jan 16, 2017 at 04:58:49PM -0800, Jeremy McNicoll wrote:
> Node names cannot have an underscore '_' in the name.
> Simply rename 'rpm_request' nodes to 'rpm-request'.
>
> Signed-off-by: Jeremy McNicoll <jeremymc@redhat.com>
> ---
> Documentation/devicetree/bindings/clock/qcom,rpmcc.txt | 2 +-
> .../devicetree/bindings/regulator/qcom,smd-rpm-regulator.txt | 2 +-
> Documentation/devicetree/bindings/soc/qcom/qcom,smd-rpm.txt | 6 +++---
> Documentation/devicetree/bindings/soc/qcom/qcom,smd.txt | 2 +-
> arch/arm/boot/dts/qcom-apq8074-dragonboard.dts | 2 +-
> arch/arm/boot/dts/qcom-apq8084.dtsi | 2 +-
> arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dts | 2 +-
> arch/arm/boot/dts/qcom-msm8974-sony-xperia-honami.dts | 2 +-
> arch/arm/boot/dts/qcom-msm8974.dtsi | 2 +-
> arch/arm64/boot/dts/qcom/msm8916.dtsi | 2 +-
> arch/arm64/boot/dts/qcom/msm8994-smd-rpm.dtsi | 2 +-
> 11 files changed, 13 insertions(+), 13 deletions(-)
>
Just in case someone trips over this thread in the future.
Table 2.1 from http://www.devicetree.org/specifications-pdf
provides useful information on naming conventions.
-jeremy
prev parent reply other threads:[~2017-01-23 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 0:58 [PATCH V2 0/4] Enable onboard SDHCI for Nexus 5X (msm8992) Jeremy McNicoll
[not found] ` <1484614729-26751-1-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-17 0:58 ` [PATCH V2 1/4] clk: gcc: Updates for SDHCI enablement Jeremy McNicoll
2017-01-17 23:25 ` Stephen Boyd
[not found] ` <20170117232542.GV17126-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-01-18 20:14 ` Jeremy McNicoll
2017-01-17 0:58 ` [PATCH V2 2/4] sdhci: Add quirk for delayed IRQ ACK Jeremy McNicoll
2017-01-17 0:58 ` [PATCH V2 3/4] arm64: dts: Enable SDHCI for Nexus 5X (msm8992) Jeremy McNicoll
[not found] ` <1484614729-26751-4-git-send-email-jeremymc-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-18 19:02 ` Bjorn Andersson
2017-01-20 0:20 ` Jeremy McNicoll
2017-01-19 17:21 ` Rob Herring
2017-01-17 0:58 ` [PATCH V2 4/4] dts: doc: rename rpm_requests to respect DT naming conventions Jeremy McNicoll
2017-01-19 17:22 ` Rob Herring
2017-01-23 10:39 ` Jeremy McNicoll [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=20170123103947.GA22659@mini-rhel.redhat.com \
--to=jmcnicol@redhat.com \
--cc=andy.gross@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=git@kchr.de \
--cc=jeremymc@redhat.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=riteshh@codeaurora.org \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--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).