Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Imran Shaik <quic_imrashai@quicinc.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
	Melody Olvera <quic_molvera@quicinc.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Andy Gross <agross@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org,
	Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Jagadeesh Kona <quic_jkona@quicinc.com>,
	Rob Herring <robh+dt@kernel.org>,
	Ajit Pandey <quic_ajipan@quicinc.com>,
	linux-kernel@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Taniya Das <quic_tdas@quicinc.com>
Subject: Re: [PATCH V2 1/5] dt-bindings: clock: Update GCC clocks for QDU1000 and QRU1000 SoCs
Date: Wed, 28 Jun 2023 09:50:20 -0600	[thread overview]
Message-ID: <168796741983.536728.7220713393187676699.robh@kernel.org> (raw)
In-Reply-To: <20230628092837.3090801-2-quic_imrashai@quicinc.com>


On Wed, 28 Jun 2023 14:58:33 +0530, Imran Shaik wrote:
> Update the qcom GCC clock bindings for QDU1000 and QRU1000 SoCs.
> 
> Co-developed-by: Taniya Das <quic_tdas@quicinc.com>
> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
> Signed-off-by: Imran Shaik <quic_imrashai@quicinc.com>
> ---
> Chanes since v1:
>  - Removed the v2 variant compatible string changes
>  - Updated the maintainers list
> 
>  Documentation/devicetree/bindings/clock/qcom,qdu1000-gcc.yaml | 3 ++-
>  include/dt-bindings/clock/qcom,qdu1000-gcc.h                  | 4 +++-
>  2 files changed, 5 insertions(+), 2 deletions(-)
> 

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


  parent reply	other threads:[~2023-06-28 15:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  9:28 [PATCH V2 0/5] Update GCC clocks for QDU1000 and QRU1000 SoCs Imran Shaik
2023-06-28  9:28 ` [PATCH V2 1/5] dt-bindings: clock: " Imran Shaik
2023-06-28 10:18   ` Rob Herring
2023-06-28 15:50   ` Rob Herring [this message]
2023-06-28  9:28 ` [PATCH V2 2/5] clk: qcom: gcc-qdu1000: Fix gcc_pcie_0_pipe_clk_src clock handling Imran Shaik
2023-06-28 11:03   ` Konrad Dybcio
2023-06-28  9:28 ` [PATCH V2 3/5] clk: qcom: gcc-qdu1000: Update GCC clocks as per the latest hw version Imran Shaik
2023-06-28 11:06   ` Konrad Dybcio
2023-07-06 10:51     ` Imran Shaik
2023-07-06 10:59       ` Konrad Dybcio
2023-06-28  9:28 ` [PATCH V2 4/5] clk: qcom: gcc-qdu1000: Add support for GDSCs Imran Shaik
2023-06-28 11:08   ` Konrad Dybcio
2023-06-28  9:28 ` [PATCH V2 5/5] clk: qcom: gcc-qdu1000: Update the RCGs ops Imran Shaik
2023-06-28 11:08   ` Konrad Dybcio

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=168796741983.536728.7220713393187676699.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=agross@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=quic_ajipan@quicinc.com \
    --cc=quic_imrashai@quicinc.com \
    --cc=quic_jkona@quicinc.com \
    --cc=quic_molvera@quicinc.com \
    --cc=quic_skakitap@quicinc.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh+dt@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