public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Douglas Anderson <dianders@chromium.org>
Cc: sboyd@kernel.org, andy.gross@linaro.org, tdas@codeaurora.org,
	girishm@codeaurora.org, linux-arm-msm@vger.kernel.org,
	anischal@codeaurora.org, bjorn.andersson@linaro.org,
	grahamr@codeaurora.org, linux-soc@vger.kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 1/2] clk: qcom: Add qspi (Quad SPI) clock defines for sdm845 to header
Date: Wed, 25 Jul 2018 10:01:02 -0600	[thread overview]
Message-ID: <20180725160102.GA18545@rob-hp-laptop> (raw)
In-Reply-To: <20180724174513.174018-2-dianders@chromium.org>

On Tue, Jul 24, 2018 at 10:45:12AM -0700, Douglas Anderson wrote:
> These clocks will need to be defined in the clock driver and
> referenced in device tree files.
> 
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
> 
> Changes in v3: None
> Changes in v2: None
> 
>  include/dt-bindings/clock/qcom,gcc-sdm845.h | 3 +++
>  1 file changed, 3 insertions(+)

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2018-07-25 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 17:45 [PATCH v3 0/2] clk: qcom: Quad SPI (qspi) clock support for sdm845 Douglas Anderson
2018-07-24 17:45 ` [PATCH v3 1/2] clk: qcom: Add qspi (Quad SPI) clock defines for sdm845 to header Douglas Anderson
2018-07-25 16:01   ` Rob Herring [this message]
2018-08-10  8:08     ` Taniya Das
2018-08-28 22:58   ` Stephen Boyd
2018-07-24 17:45 ` [PATCH v3 2/2] clk: qcom: Add qspi (Quad SPI) clocks for sdm845 Douglas Anderson
2018-07-24 18:24   ` Doug Anderson
2018-08-10  8:09   ` Taniya Das
2018-08-28 22:58   ` Stephen Boyd

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=20180725160102.GA18545@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=andy.gross@linaro.org \
    --cc=anischal@codeaurora.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=girishm@codeaurora.org \
    --cc=grahamr@codeaurora.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=sboyd@kernel.org \
    --cc=tdas@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