From: Bjorn Andersson <andersson@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Taniya Das <taniya.das@oss.qualcomm.com>
Cc: Ajit Pandey <quic_ajipan@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 0/2] Add support for Display clock controllers for Glymur SoC
Date: Thu, 4 Sep 2025 09:35:36 -0500 [thread overview]
Message-ID: <175699653015.2182903.5847736371433718879.b4-ty@kernel.org> (raw)
In-Reply-To: <20250829-glymur-disp-clock-controllers-v1-0-0ce6fabd837c@oss.qualcomm.com>
On Fri, 29 Aug 2025 13:28:02 +0530, Taniya Das wrote:
> Introduce the support for Display clock controller(DISPCC) for
>
> Qualcomm's next gen compute SoC - Glymur.
>
> Device tree changes aren't part of this series and will be posted separately after the
> official announcement of the Glymur SoC.
>
> [...]
Applied, thanks!
[2/2] clk: qcom: dispcc-glymur: Add support for Display Clock Controller
commit: b4d15211c4086a8a6d670cdba9649112fed67f86
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-09-04 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 7:58 Taniya Das
2025-08-29 7:58 ` [PATCH 1/2] dt-bindings: clock: Add DISPCC and reset controller for GLYMUR SoC Taniya Das
2025-08-29 8:12 ` Dmitry Baryshkov
2025-08-29 8:24 ` Taniya Das
2025-09-02 8:21 ` Krzysztof Kozlowski
2025-08-29 7:58 ` [PATCH 2/2] clk: qcom: dispcc-glymur: Add support for Display Clock Controller Taniya Das
2025-08-29 8:15 ` Dmitry Baryshkov
2025-09-04 14:35 ` Bjorn Andersson [this message]
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=175699653015.2182903.5847736371433718879.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=taniya.das@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®