From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Conor Dooley <conor@kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] soc: qcom: llcc: Fix usecase id macro alignment
Date: Wed, 26 Nov 2025 18:43:19 +0100 [thread overview]
Message-ID: <8078408c-b4c4-426f-8801-902b2b6dfd71@kernel.org> (raw)
In-Reply-To: <7158bde2-bf70-4a2d-b19f-fcc24cc37d28@oss.qualcomm.com>
On 26/11/2025 12:38, Pankaj Patil wrote:
> On 11/26/2025 2:29 PM, Krzysztof Kozlowski wrote:
>> On Tue, Nov 25, 2025 at 02:46:23PM +0530, Pankaj Patil wrote:
>>> Aligned macro values for usecase id along the column length
>>> -#define LLCC_CAMOFE 71
>>> -#define LLCC_CAMRTIP 72
>>> -#define LLCC_CAMSRTIP 73
>>> -#define LLCC_CAMRTRF 74
>>> -#define LLCC_CAMSRTRF 75
>>> -#define LLCC_VIDEO_APV 83
>>> -#define LLCC_COMPUTE1 87
>>> -#define LLCC_CPUSS_OPP 88
>>> -#define LLCC_CPUSSMPAM 89
>>> -#define LLCC_CAM_IPE_STROV 92
>>> -#define LLCC_CAM_OFE_STROV 93
>>> -#define LLCC_CPUSS_HEU 94
>>> -#define LLCC_MDM_PNG_FIXED 100
>>> +#define LLCC_CPUSS 1
>>> +#define LLCC_VIDSC0 2
>>> +#define LLCC_VIDSC1 3
>>> +#define LLCC_ROTATOR 4
>>> +#define LLCC_VOICE 5
>> This does not look right - you still have here spaces, so nothing fixed.
>>
>> I don't think this change is useful. You replaced one poor alignment
>> into another poor alignment, so IMO better not to touch this at all.
>>
>> Best regards,
>> Krzysztof
>>
> Sure, Will drop this patch in next revision
If fixing this, fix correctly, so these should be tabs accommodating
future IDs, so you won't be doing the same every 3 months.
But to me it is a bit of churn, does not improve readability and
actually affects negatively git blame and backporting, so I would
propose to drop it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-26 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 9:16 [PATCH v2 0/3] soc: qcom: llcc: Add support for Glymur SoC Pankaj Patil
2025-11-25 9:16 ` [PATCH v2 1/3] dt-bindings: cache: qcom,llcc: Document Glymur LLCC block Pankaj Patil
2025-11-26 8:54 ` Krzysztof Kozlowski
2025-11-25 9:16 ` [PATCH v2 2/3] soc: qcom: llcc: Fix usecase id macro alignment Pankaj Patil
2025-11-26 8:59 ` Krzysztof Kozlowski
2025-11-26 11:38 ` Pankaj Patil
2025-11-26 17:17 ` Bjorn Andersson
2025-11-26 17:43 ` Krzysztof Kozlowski [this message]
2025-11-25 9:16 ` [PATCH v2 3/3] soc: qcom: llcc-qcom: Add support for Glymur Pankaj Patil
2025-11-27 10:22 ` Konrad Dybcio
2025-11-27 10:37 ` Pankaj Patil
2025-11-27 10:43 ` Konrad Dybcio
2025-11-28 9:47 ` 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=8078408c-b4c4-426f-8801-902b2b6dfd71@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).