From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kaipeng Zeng <kaipeng94@gmail.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org, konradybcio@kernel.org,
andersson@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: Add Acer Swift Go Pro AI (SFA14-11)
Date: Sun, 5 Jul 2026 17:39:29 +0200 [thread overview]
Message-ID: <2392702d-d2e9-4537-ae51-9c6b619ec334@kernel.org> (raw)
In-Reply-To: <68b83361-42a5-45ac-8441-f0661b005f85@gmail.com>
On 05/07/2026 17:34, Kaipeng Zeng wrote:
>>> e.g. microsoft,denali that you mentioned is a MS codename for the
>>> Surface Pro something something
>>
>> I am fine with mixing (swift-go-sfa14-11), but the model number alone is
>> very hard to parse by humans.
>>
>> Best regards,
>> Krzysztof
>
> Initially, I chose the model number because Acer has several QCOM
> powered laptops with similar product names:
> - Acer Swift Go Pro AI (SFA14-11)
> - Acer Swift Go 14 AI (SFG14-*)
> - Acer Swift Spin 14 AI (SFSP14-Q51T)
> - Acer Swift 14 AI (SF14-11*)
>
> Using the product name directly here can be confusing.
> I think using a mixed name (swift-go-sfa14-11) is better, too.
>
All the names are different, so I do not see confusion.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-05 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:31 [PATCH 0/2] Add device tree for Acer Swift Go Pro AI (SFA14-11) Kaipeng Zeng
2026-07-02 6:31 ` [PATCH 1/2] dt-bindings: arm: qcom: Add " Kaipeng Zeng
2026-07-02 6:27 ` Krzysztof Kozlowski
2026-07-02 6:35 ` Krzysztof Kozlowski
2026-07-02 9:29 ` Konrad Dybcio
2026-07-02 9:32 ` Krzysztof Kozlowski
2026-07-05 15:34 ` Kaipeng Zeng
2026-07-05 15:39 ` Krzysztof Kozlowski [this message]
2026-07-02 6:31 ` [PATCH 2/2] arm64: dts: qcom: Add support for " Kaipeng Zeng
2026-07-02 6:31 ` Krzysztof Kozlowski
2026-07-02 6:40 ` sashiko-bot
2026-07-02 11:45 ` Konrad Dybcio
2026-07-05 15:29 ` Kaipeng Zeng
2026-07-06 10:37 ` Konrad Dybcio
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=2392702d-d2e9-4537-ae51-9c6b619ec334@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kaipeng94@gmail.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@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