From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
devicetree@vger.kernel.org
Cc: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Benson Leung <bleung@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mfd: cros-ec: Fix indentation in the example
Date: Fri, 6 Mar 2020 10:07:31 +0100 [thread overview]
Message-ID: <32848672-85ab-5ed2-731c-bfd4dfa62760@collabora.com> (raw)
In-Reply-To: <20200305223631.27550-1-j.neuschaefer@gmx.net>
Hi Jonathan,
On 5/3/20 23:36, Jonathan Neuschäfer wrote:
> Properties get one more level of indentation than the node they are in.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
> Documentation/devicetree/bindings/mfd/cros-ec.txt | 6 +++---
Thanks for sending the patch but the binding is in process to be converted to
json-schema right now [1], and this change will not be needed.
Thanks,
Enric
[1] https://patchwork.ozlabs.org/patch/1250141/
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mfd/cros-ec.txt b/Documentation/devicetree/bindings/mfd/cros-ec.txt
> index 4860eabd0f72..3bf9d0868b98 100644
> --- a/Documentation/devicetree/bindings/mfd/cros-ec.txt
> +++ b/Documentation/devicetree/bindings/mfd/cros-ec.txt
> @@ -65,9 +65,9 @@ spi@131b0000 {
> wakeup-source;
> spi-max-frequency = <5000000>;
> controller-data {
> - cs-gpio = <&gpf0 3 4 3 0>;
> - samsung,spi-cs;
> - samsung,spi-feedback-delay = <2>;
> + cs-gpio = <&gpf0 3 4 3 0>;
> + samsung,spi-cs;
> + samsung,spi-feedback-delay = <2>;
> };
> };
> };
> --
> 2.20.1
>
next prev parent reply other threads:[~2020-03-06 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 22:36 [PATCH] dt-bindings: mfd: cros-ec: Fix indentation in the example Jonathan Neuschäfer
2020-03-06 9:07 ` Enric Balletbo i Serra [this message]
2020-03-06 10:58 ` Jonathan Neuschäfer
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=32848672-85ab-5ed2-731c-bfd4dfa62760@collabora.com \
--to=enric.balletbo@collabora.com \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=groeck@chromium.org \
--cc=j.neuschaefer@gmx.net \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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