From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Kaipeng Zeng <kaipeng94@gmail.com>
Cc: Jianfeng Liu <liujianfeng1994@gmail.com>,
jactry92@gmail.com, andersson@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, konradybcio@kernel.org,
krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
robh@kernel.org, krzysztof.kozlowski@oss.qualcomm.com
Subject: Re: [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI
Date: Thu, 22 Oct 2026 10:00:12 +0200 [thread overview]
Message-ID: <f5d77b3d-a6b3-42ea-8b20-939a301ae331@oss.qualcomm.com> (raw)
In-Reply-To: <CAHk8ZdvrVt8TkZrSd7qyzi5AirL+FtwUpHT0QLcUd5qBJmhy+w@mail.gmail.com>
On 10/22/26 8:15 AM, Kaipeng Zeng wrote:
> Hi Konrad,
>
> Thanks for your reply.
>
> On Wed, Oct 21, 2026 at 8:48 PM Konrad Dybcio
> <konrad.dybcio@oss.qualcomm.com> wrote:
>>
>> This makes it sound like the retailer made up / confused some names,
>> let's just go with what the manufacturer says
>>
>
> Just want to make sure I don't misunderstand anything, if this is what
> you preferred:
> ```
> model = "Acer Swift Go Pro AI (SFA14-11)";
> compatible = "acer,swift-sfa14-11", "qcom,x1e78100", "qcom,x1e80100";
My reading of Jianfeng's email is that the "Go Pro AI" part does
not appear on the Acer sites
Konrad
next prev parent reply other threads:[~2026-10-22 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 8:54 [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI (SFA14-11) Kaipeng Zeng
2026-10-06 8:54 ` [PATCH v4 1/2] dt-bindings: arm: qcom: Add " Kaipeng Zeng
2026-10-06 8:54 ` [PATCH v4 2/2] arm64: dts: qcom: Add support for " Kaipeng Zeng
2026-10-06 9:07 ` sashiko-bot
2026-10-08 10:34 ` [PATCH v4 0/2] Add device tree " Jianfeng Liu
2026-10-12 8:15 ` Kaipeng Zeng
2026-10-12 10:03 ` Jianfeng Liu
2026-10-12 14:18 ` Jactry Zeng
2026-10-13 1:57 ` [PATCH v4 0/2] Add device tree for Acer Swift Go Pro AI Jianfeng Liu
2026-10-21 12:47 ` Konrad Dybcio
2026-10-22 6:15 ` Kaipeng Zeng
2026-10-22 8:00 ` Konrad Dybcio [this message]
2026-10-22 9:03 ` Kaipeng Zeng
2026-10-23 13:00 ` 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=f5d77b3d-a6b3-42ea-8b20-939a301ae331@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jactry92@gmail.com \
--cc=kaipeng94@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=liujianfeng1994@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.