From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Chen <peter.chen@cixtech.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Fugang Duan <fugang.duan@cixtech.com>,
CIX Linux Kernel Upstream Group <cix-kernel-upstream@cixtech.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: cix: Use lowercase hex
Date: Mon, 29 Dec 2025 08:17:15 +0100 [thread overview]
Message-ID: <88e9e4c4-13c9-4b96-88cc-abb581011e87@kernel.org> (raw)
In-Reply-To: <aVHb-kbi2QbChxj9@nchen-desktop>
On 29/12/2025 02:40, Peter Chen wrote:
> On 25-12-23 16:24:25, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL
>>
>> The DTS code coding style expects lowercase hex for values and unit
>> addresses.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>>
>> ---
>>
>> Patches done with sed, verified with comparing unflattened DTB and
>> dtx_diff.
>> ---
>> arch/arm64/boot/dts/cix/sky1.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/cix/sky1.dtsi b/arch/arm64/boot/dts/cix/sky1.dtsi
>> index 64b76905cbff..fb8c826bbc97 100644
>> --- a/arch/arm64/boot/dts/cix/sky1.dtsi
>> +++ b/arch/arm64/boot/dts/cix/sky1.dtsi
>> @@ -523,7 +523,7 @@ pcie_x1_1_rc: pcie@a0e0000 {
>> reg-names = "reg", "cfg", "rcsu_strap", "rcsu_status", "msg";
>> ranges = <0x01000000 0x0 0x38100000 0x0 0x38100000 0x0 0x00100000>,
>> <0x02000000 0x0 0x38200000 0x0 0x38200000 0x0 0x07e00000>,
>> - <0x43000000 0x0C 0x00000000 0x0C 0x00000000 0x04 0x00000000>;
>> + <0x43000000 0x0c 0x00000000 0x0c 0x00000000 0x04 0x00000000>;
>
> Sorry, I could not apply for v6.19-rc1, could you?
What do you mean? It applies cleanly on v6.19-rc1 and on next. Your
branches are not really updated, so maybe you need to fix this.
And no, I cannot apply this, because this would mean CIX is
legacy/abandoned platform. Shall I mark it as such?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-29 7:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 15:24 [PATCH] arm64: dts: cix: Use lowercase hex Krzysztof Kozlowski
2025-12-29 1:40 ` Peter Chen
2025-12-29 7:17 ` Krzysztof Kozlowski [this message]
2025-12-30 2:05 ` Peter Chen
2025-12-30 7:19 ` 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=88e9e4c4-13c9-4b96-88cc-abb581011e87@kernel.org \
--to=krzk@kernel.org \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fugang.duan@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@cixtech.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