linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Rob Herring <robh@kernel.org>
Cc: Tirupathi Reddy <tirupath@codeaurora.org>,
	mturquette@baylibre.com, mark.rutland@arm.com,
	andy.gross@linaro.org, david.brown@linaro.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-soc@vger.kernel.org
Subject: Re: [PATCH V7 2/2] dt-bindings: Add qcom spmi_pmic clock divider bindings
Date: Wed, 6 Dec 2017 22:28:24 -0800	[thread overview]
Message-ID: <20171207062824.GJ4283@codeaurora.org> (raw)
In-Reply-To: <20171204202959.6gxmy7jdt7gwspuh@rob-hp-laptop>

On 12/04, Rob Herring wrote:
> On Tue, Nov 21, 2017 at 02:41:05PM +0530, Tirupathi Reddy wrote:
> > This patch adds device tree bindings for Qualcomm SPMI PMIC
> > clock divider module.
> > 
> > Signed-off-by: Tirupathi Reddy <tirupath@codeaurora.org>
> > ---
> >  .../bindings/clock/qcom,spmi-pmic-div.txt          | 59 ++++++++++++++++++++++
> 
> Didn't Stephen say to move this somewhere else?

yeah I'll move it to qcom,spmi-clkdiv.txt

> > +
> > +- clock-cells:
> 
> #clock-cells
> 

And fix this. Thanks.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-12-07  6:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  9:11 [PATCH V7 0/2] clk: qcom: spmi_pmic clock divider support Tirupathi Reddy
2017-11-21  9:11 ` [PATCH V7 1/2] clk: qcom: Add " Tirupathi Reddy
2017-12-07  6:32   ` Stephen Boyd
2017-11-21  9:11 ` [PATCH V7 2/2] dt-bindings: Add qcom spmi_pmic clock divider bindings Tirupathi Reddy
2017-12-04 20:29   ` Rob Herring
2017-12-07  6:28     ` Stephen Boyd [this message]
2017-12-07  6:32   ` Stephen Boyd
2017-12-04 10:48 ` [PATCH V7 0/2] clk: qcom: spmi_pmic clock divider support Tirupathi Reddy 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=20171207062824.GJ4283@codeaurora.org \
    --to=sboyd@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=mark.rutland@arm.com \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=tirupath@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;
as well as URLs for NNTP newsgroup(s).