From: "Andreas Färber" <afaerber@suse.de>
To: Mark Rutland <mark.rutland@arm.com>,
Doug Anderson <dianders@chromium.org>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
Stephan van Schaik <stephan@synkhronix.com>,
Vincent Palatin <vpalatin@chromium.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Randy Dunlap <rdunlap@infradead.org>,
Mark Brown <broonie@linaro.org>, Simon Glass <sjg@chromium.org>,
Michael Spang <spang@chromium.org>,
"OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
DOCUMENTATION <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] Documentation: devicetree: Fix tps65090 typos
Date: Wed, 25 Jun 2014 13:43:18 +0200 [thread overview]
Message-ID: <53AAB5D6.50500@suse.de> (raw)
In-Reply-To: <20140625104732.GE14495@leverpostej>
Am 25.06.2014 12:47, schrieb Mark Rutland:
> On Mon, Jun 23, 2014 at 06:27:04PM +0100, Doug Anderson wrote:
>> Andreas,
>>
>> On Sun, Jun 22, 2014 at 6:21 PM, Andreas Färber <afaerber@suse.de> wrote:
>>> It's vsys-l{1,2}-supply, not vsys_l{1,2}-supply.
>>>
>>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>>> ---
>>> Documentation/devicetree/bindings/regulator/tps65090.txt | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/regulator/tps65090.txt b/Documentation/devicetree/bindings/regulator/tps65090.txt
>>> index 34098023..ca69f5e 100644
>>> --- a/Documentation/devicetree/bindings/regulator/tps65090.txt
>>> +++ b/Documentation/devicetree/bindings/regulator/tps65090.txt
>>> @@ -45,8 +45,8 @@ Example:
>>> infet5-supply = <&some_reg>;
>>> infet6-supply = <&some_reg>;
>>> infet7-supply = <&some_reg>;
>>> - vsys_l1-supply = <&some_reg>;
>>> - vsys_l2-supply = <&some_reg>;
>>> + vsys-l1-supply = <&some_reg>;
>>> + vsys-l2-supply = <&some_reg>;
>>
>> Your change matches the code and all existing device trees in the
>> Linux kernel.
>
> Could this fact please be mentioned in the commit message?
Yes, I admit the commit message could've been clearer in stating that
only the example is modified, not the actual specification. What about:
"Specification and existing device trees use vsys-l{1,2}-supply, not
vsys_l{1,2}-supply. Fix the example to match the specification."
Maybe also "... typos in example" in the subject.
Let me know whether I should send a v2 or let maintainers fix it up.
Regards,
Andreas
> Given that:
>
> Acked-by: Mark Rutland <mark.rutland@arm.com>
>
>> I also see plenty of other bindings with dashes, so this seems
>> reasonable.
>
> Dashes rather than underscores are preferred/correct for property names
> and compatible strings. Given no-one can possibly be using the
> bad/incorrect form with underscores, fixing the documentation to use
> dashes makes sense.
>
> Thanks,
> Mark.
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-06-25 11:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1403486483-4063-1-git-send-email-afaerber@suse.de>
2014-06-23 1:21 ` [PATCH 1/4] Documentation: devicetree: Fix s2mps11 and s5m8767 typos Andreas Färber
2014-06-23 3:21 ` Sachin Kamat
2014-06-23 23:06 ` Andreas Färber
2014-06-23 23:20 ` Doug Anderson
2014-06-23 8:15 ` Lee Jones
2014-06-23 1:21 ` [PATCH 2/4] Documentation: devicetree: Fix s2mps11 example syntax Andreas Färber
2014-06-23 3:23 ` Sachin Kamat
2014-06-23 8:15 ` Lee Jones
2014-06-23 1:21 ` [PATCH 3/4] Documentation: devicetree: Fix tps65090 typos Andreas Färber
2014-06-23 17:27 ` Doug Anderson
2014-06-25 10:47 ` Mark Rutland
2014-06-25 11:43 ` Andreas Färber [this message]
2014-06-25 12:23 ` Rob Herring
2014-06-23 1:21 ` [RFC 4/4] ARM: dts: exynos5250: Add Spring device tree Andreas Färber
2014-06-23 19:47 ` Doug Anderson
2014-06-23 22:46 ` Andreas Färber
2014-06-24 4:05 ` Doug Anderson
[not found] ` <CAD=FV=W96QpDhh1NSaVwrXYjL6Jr-v4sq1-eRSfT=tErw_KCOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-24 10:06 ` Javier Martinez Canillas
2014-06-24 15:20 ` Doug Anderson
2014-06-24 15:03 ` Vincent Palatin
2014-06-24 15:06 ` Vincent Palatin
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=53AAB5D6.50500@suse.de \
--to=afaerber@suse.de \
--cc=Pawel.Moll@arm.com \
--cc=broonie@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sjg@chromium.org \
--cc=spang@chromium.org \
--cc=stephan@synkhronix.com \
--cc=vpalatin@chromium.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).