devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	quic_schowdhu@quicinc.com, agross@kernel.org,
	andersson@kernel.org, konrad.dybcio@linaro.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	bhupesh.linux@gmail.com, krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH 2/2] dt-bindings: soc: qcom: eud: Fix identation issues in the example
Date: Sun, 8 Jan 2023 10:12:37 -0600	[thread overview]
Message-ID: <20230108161237.GA7662-robh@kernel.org> (raw)
In-Reply-To: <20230104091922.3959602-3-bhupesh.sharma@linaro.org>

On Wed, Jan 04, 2023 at 02:49:22PM +0530, Bhupesh Sharma wrote:
> As noted by Konrad while reviewing [1], the example
> node in the EUD yaml documentation has identation
> issues.

I don't see any indentation changes...

> 
> So fix them.
> 
> [1]. https://lore.kernel.org/linux-arm-msm/20221231131945.3286639-1-bhupesh.sharma@linaro.org
> 
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org>
> ---
>  Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> index c98aab209bc5d..385ebd7cbbf0c 100644
> --- a/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> +++ b/Documentation/devicetree/bindings/soc/qcom/qcom,eud.yaml
> @@ -55,9 +55,10 @@ additionalProperties: false
>  examples:
>    - |
>      eud@88e0000 {
> -           compatible = "qcom,sc7280-eud","qcom,eud";
> -           reg = <0x88e0000 0x2000>,
> -                 <0x88e2000 0x1000>;
> +           compatible = "qcom,sc7280-eud", "qcom,eud";
> +           reg = <0 0x88e0000 0 0x2000>,
> +                 <0 0x88e2000 0 0x1000>;
> +
>             ports {
>                     #address-cells = <1>;
>                     #size-cells = <0>;
> @@ -67,6 +68,7 @@ examples:
>                                     remote-endpoint = <&usb2_role_switch>;
>                             };
>                     };
> +
>                     port@1 {
>                             reg = <1>;
>                             eud_con: endpoint {
> -- 
> 2.38.1
> 
> 

  parent reply	other threads:[~2023-01-08 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  9:19 [PATCH 0/2] Fix EUD dt-binding doc & sc7280 EUD node syntax Bhupesh Sharma
2023-01-04  9:19 ` [PATCH 1/2] arm64: dts: qcom: sc7280: Fix EUD dt " Bhupesh Sharma
2023-01-04  9:19 ` [PATCH 2/2] dt-bindings: soc: qcom: eud: Fix identation issues in the example Bhupesh Sharma
2023-01-05  2:53   ` Rob Herring
2023-01-06  6:48     ` Bhupesh Sharma
2023-01-08 16:12   ` Rob Herring [this message]
2023-05-25  4:53 ` (subset) [PATCH 0/2] Fix EUD dt-binding doc & sc7280 EUD node syntax Bjorn Andersson

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=20230108161237.GA7662-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.linux@gmail.com \
    --cc=bhupesh.sharma@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_schowdhu@quicinc.com \
    /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).