From: Taniya Das <tdas@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: clock: Add YAML schemas for the QCOM RPMHCC clock bindings
Date: Tue, 29 Oct 2019 23:18:02 +0530 [thread overview]
Message-ID: <e52cc998-85aa-6421-5bf1-b1e55f260bcc@codeaurora.org> (raw)
In-Reply-To: <20191029020450.GA16322@bogus>
Hello Rob,
Thanks for the review. I will fix the below in the next patch.
On 10/29/2019 7:34 AM, Rob Herring wrote:
>> +properties:
>> + compatible :
> drop space ^
>
>> + enum:
>> + - qcom,sdm845-rpmh-clk
>> + - qcom,sm8150-rpmh-clk
> Wrong indent (1 char too many).
>
>> +
>> + clocks:
>> + maxItems: 1
>> +
>> + clock-names:
>> + maxItems: 1
> Can drop this. Implied by items list.
>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
next prev parent reply other threads:[~2019-10-29 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 10:09 [PATCH v1 0/3] Add support for RPMHCC for SC7180 Taniya Das
2019-10-18 10:09 ` [PATCH v1 1/3] dt-bindings: clock: Add YAML schemas for the QCOM RPMHCC clock bindings Taniya Das
2019-10-29 2:04 ` Rob Herring
2019-10-29 17:48 ` Taniya Das [this message]
2019-10-18 10:09 ` [PATCH v1 2/3] dt-bindings: clock: Introduce RPMHCC bindings for SC7180 Taniya Das
2019-10-29 12:27 ` Rob Herring
2019-10-18 10:09 ` [PATCH v1 3/3] clk: qcom: clk-rpmh: Add support for RPMHCC " Taniya Das
2019-10-21 12:53 ` Vinod Koul
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=e52cc998-85aa-6421-5bf1-b1e55f260bcc@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=robh@kernel.org \
--cc=sboyd@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).