From: Krzysztof Kozlowski <krzk@kernel.org>
To: Taniya Das <taniya.das@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Ajit Pandey <ajit.pandey@oss.qualcomm.com>,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Jagadeesh Kona <jagadeesh.kona@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: defconfig: Enable Glymur clock controllers
Date: Fri, 20 Feb 2026 12:07:57 +0100 [thread overview]
Message-ID: <db6b5e85-bf19-45dc-b536-75512096a5f9@kernel.org> (raw)
In-Reply-To: <20260220-glymur_mmcc_dt_config-v1-2-e0e2f43a32af@oss.qualcomm.com>
On 20/02/2026 11:16, Taniya Das wrote:
> Enable the Glymur video and gpu clock controller for their respective
Qualcomm Glymur SoC
> functionalities on the Qualcomm Glymur CRD boards.
Subject: Qualcomm
Again, you are adding commit to generic kernel to generic defconfig. How
anyone can figure out what is Glymur when going via shortlog?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-20 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 10:16 [PATCH 0/2] clk: qcom: Add device tree and enable clocks for Glymur Taniya Das
2026-02-20 10:16 ` [PATCH 1/2] arm64: dts: qcom: Add support for MM clock controllers " Taniya Das
2026-02-20 10:42 ` Konrad Dybcio
2026-02-20 10:16 ` [PATCH 2/2] arm64: defconfig: Enable Glymur clock controllers Taniya Das
2026-02-20 11:07 ` Krzysztof Kozlowski [this message]
2026-02-20 14:24 ` Taniya Das
2026-02-20 18:33 ` [PATCH 0/2] clk: qcom: Add device tree and enable clocks for Glymur Dmitry Baryshkov
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=db6b5e85-bf19-45dc-b536-75512096a5f9@kernel.org \
--to=krzk@kernel.org \
--cc=ajit.pandey@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imran.shaik@oss.qualcomm.com \
--cc=jagadeesh.kona@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
Powered by JetHome