From: Gabor Juhos <j4g8y7@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: ipq5018-tplink-archer-ax55-v1: use 'ipq0518' prefix for dts
Date: Fri, 9 Oct 2026 15:30:45 +0200 [thread overview]
Message-ID: <1796fd45-50aa-40a3-bccb-d779559ca02d@gmail.com> (raw)
In-Reply-To: <ca27b076-1814-4780-80f1-d022183736cf@kernel.org>
2026. 10. 09. 12:15 keltezéssel, Krzysztof Kozlowski írta:
> On 07/10/2026 18:59, Gabor Juhos wrote:
>> The TP-Link Archer AX55 v1 board is based on the IPQ0518 SoC.
>> Change the prefix of the board dts to reflect that.
>>
>> Signed-off-by: Gabor Juhos <j4g8y7@gmail.com>
>> ---
>> arch/arm64/boot/dts/qcom/Makefile | 2 +-
>> ...5018-tplink-archer-ax55-v1.dts => ipq0518-tplink-archer-ax55-v1.dts} | 0
>
> No, this just breaks whatever scripts people have for no real gain.
> Assuming 0518 exists, then still 5018 is as good prefix.
Ok, will drop this one.
Regards,
Gabor
prev parent reply other threads:[~2026-10-09 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 16:59 [PATCH 0/3] add 'qcom,ipq0518' compatible for the TP-Link Archer AX55 v1 Gabor Juhos
2026-10-07 16:59 ` [PATCH 1/3] dt-bindings: arm: qcom: add 'qcom,ipq0518' compatible for " Gabor Juhos
2026-10-07 16:59 ` [PATCH 2/3] arm64: dts: qcom: ipq5018-tplink-archer-ax55-v1: add 'qcom,ipq0518' compatible Gabor Juhos
2026-10-07 16:59 ` [PATCH 3/3] arm64: dts: qcom: ipq5018-tplink-archer-ax55-v1: use 'ipq0518' prefix for dts Gabor Juhos
2026-10-09 10:15 ` Krzysztof Kozlowski
2026-10-09 13:30 ` Gabor Juhos [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=1796fd45-50aa-40a3-bccb-d779559ca02d@gmail.com \
--to=j4g8y7@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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