From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2] clk: qcom: Constify qcom_cc_driver_data and list of critical CBCR registers
Date: Thu, 30 Apr 2026 16:05:39 +0200 [thread overview]
Message-ID: <828d2935-e881-443f-b0e7-eb68466ecd30@oss.qualcomm.com> (raw)
In-Reply-To: <a0a9fb8d-c109-4120-8780-8f9c21027b89@linaro.org>
On 30/04/2026 15:03, Vladimir Zapolskiy wrote:
> On 4/29/26 20:09, Krzysztof Kozlowski wrote:
>> The static 'struct qcom_cc_driver_data' and array 'xxx_critical_cbcrs'
>> are already treated by common.c code as pointers to const, so constify
>> few remaining pieces.
>>
>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>
>> ---
>>
>> Changes in v2:
>> 1. Constify also nw_gcc_nord_critical_cbcrs (Sashiko)
>> 2. Add rb tag
>> ---
>> drivers/clk/qcom/gcc-nord.c | 2 +-
>> drivers/clk/qcom/gpucc-sm8750.c | 4 ++--
>> drivers/clk/qcom/negcc-nord.c | 2 +-
>> drivers/clk/qcom/nwgcc-nord.c | 4 ++--
>> drivers/clk/qcom/segcc-nord.c | 2 +-
>> 5 files changed, 7 insertions(+), 7 deletions(-)
>
> What's about constifying video_cc_sm8550_driver_data from videocc-sm8550.c?
It's on my exception list, not sure what would be the benefit in practice.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-30 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 17:09 [PATCH v2] clk: qcom: Constify qcom_cc_driver_data and list of critical CBCR registers Krzysztof Kozlowski
2026-04-29 17:14 ` Taniya Das
2026-04-30 13:03 ` Vladimir Zapolskiy
2026-04-30 14:05 ` Krzysztof Kozlowski [this message]
2026-04-30 14:36 ` Vladimir Zapolskiy
2026-04-30 14:43 ` Krzysztof Kozlowski
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=828d2935-e881-443f-b0e7-eb68466ecd30@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=vladimir.zapolskiy@linaro.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