From: Vinod Koul <vkoul@kernel.org>
To: quic_vamslank@quicinc.com
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
mturquette@baylibre.com, sboyd@kernel.org, robh+dt@kernel.org,
tglx@linutronix.de, maz@kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
manivannan.sadhasivam@linaro.org
Subject: Re: [PATCH v5 1/6] dt-bindings: clock: Add SDX65 GCC clock bindings
Date: Mon, 22 Nov 2021 16:12:00 +0530 [thread overview]
Message-ID: <YZtz+PAWMBLGw0Dx@matsya> (raw)
In-Reply-To: <e20b452994bbd410411a631ef96091031c2fc039.1637302009.git.quic_vamslank@quicinc.com>
On 18-11-21, 22:11, quic_vamslank@quicinc.com wrote:
> From: Vamsi krishna Lanka <quic_vamslank@quicinc.com>
>
> Add device tree bindings for global clock controller on SDX65 SOCs.
Reviewed-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2021-11-22 10:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 6:11 [PATCH v5 0/6] Add Pdc, GCC and RPMh clock support for SDX65 quic_vamslank
2021-11-19 6:11 ` [PATCH v5 1/6] dt-bindings: clock: Add SDX65 GCC clock bindings quic_vamslank
2021-11-22 10:42 ` Vinod Koul [this message]
2021-11-28 23:14 ` Rob Herring
2021-11-19 6:11 ` [PATCH v5 2/6] clk: qcom: Add LUCID_EVO PLL type for SDX65 quic_vamslank
2021-11-22 10:42 ` Vinod Koul
2021-11-26 23:59 ` Bjorn Andersson
2021-11-19 6:11 ` [PATCH v5 3/6] clk: qcom: Add SDX65 GCC support quic_vamslank
2021-11-27 0:02 ` Bjorn Andersson
2021-11-19 6:11 ` [PATCH v5 4/6] dt-bindings: clock: Introduce RPMHCC bindings for SDX65 quic_vamslank
2021-11-19 6:11 ` [PATCH v5 5/6] clk: qcom: Add support for SDX65 RPMh clocks quic_vamslank
2021-11-19 6:11 ` [PATCH v5 6/6] dt-bindings: clock: Introduce pdc bindings for SDX65 quic_vamslank
2021-11-27 0:06 ` Bjorn Andersson
2021-12-01 22:26 ` Vamsi Krishna Lanka
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=YZtz+PAWMBLGw0Dx@matsya \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@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=manivannan.sadhasivam@linaro.org \
--cc=maz@kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_vamslank@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.