From: Mark Brown <broonie@kernel.org>
To: Kathiravan T <kathirav@codeaurora.org>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
lgirdwood@gmail.com, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, sivaprak@codeaurora.org
Subject: Re: [PATCH 4/6] dt-bindings: regulator: add YAML schema for QCOM SMD-RPM regulator
Date: Fri, 19 Jun 2020 11:41:52 +0100 [thread overview]
Message-ID: <20200619104152.GC5396@sirena.org.uk> (raw)
In-Reply-To: <1592550307-11040-5-git-send-email-kathirav@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Fri, Jun 19, 2020 at 12:35:05PM +0530, Kathiravan T wrote:
> Add the YAML schema for the devicetree properties used in the QCOM
> SMD-RPM driver.
Please make YAML binding conversions the last thing you do in any series
that includes them, they often require quite a few revisions and there
is often quite a backlog in YAML binding reviews which means that
everything else gets delayed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-19 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 7:05 [PATCH 0/6] Add frequency and voltage scaling support for IPQ6018 SoC Kathiravan T
2020-06-19 7:05 ` [PATCH 1/6] dt-bindings: soc: qcom: add YAML schema for SMD-RPM driver Kathiravan T
2020-07-15 19:14 ` Rob Herring
2020-06-19 7:05 ` [PATCH 2/6] dt-bindings: soc: qcom: Add IPQ6018 compatible Kathiravan T
2020-06-19 7:05 ` [PATCH 3/6] soc: qcom: smd-rpm: " Kathiravan T
2020-06-19 7:05 ` [PATCH 4/6] dt-bindings: regulator: add YAML schema for QCOM SMD-RPM regulator Kathiravan T
2020-06-19 10:41 ` Mark Brown [this message]
2020-06-19 7:05 ` [PATCH 5/6] dt-bindings: add MP5496 regulator compatible Kathiravan T
2020-06-19 7:05 ` [PATCH 6/6] regulator: qcom_smd: Add MP5496 regulators Kathiravan T
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=20200619104152.GC5396@sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kathirav@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sivaprak@codeaurora.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