mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jianfeng Liu <liujianfeng1994@gmail.com>
Cc: abelvesa@kernel.org, andersson@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, konradybcio@kernel.org,
	krzk+dt@kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm: qcom: Add Acer Swift SFA14-11
Date: Mon, 28 Sep 2026 11:32:51 +0200	[thread overview]
Message-ID: <0f3a7511-b191-43d6-893f-6ac70726a7c9@kernel.org> (raw)
In-Reply-To: <20260928082322.10078-1-liujianfeng1994@gmail.com>

On 28/09/2026 10:23, Jianfeng Liu wrote:
> On Mon, 28 Sep 2026 08:39:55 +0200, Krzysztof wrote:
>>> +              - acer,sfa14-11
>>
>> acer,swift-sfa14-11
>>
>> ?
> 
> Hi Krzysztof,
> 
> As I mentioned in the cover leter, both Swift SFA14-11 and SFA14-11 can be
> found in www.acer.com, but the UEFI firmware reports the Product Name as

I don't understand. Your commit subject says it is Swift SFA14-11.

> SFA14-11, and S in SFA should have the meaning of Swift. If you think
> acer,swift-sfa14-11 is a better one, I can update a new version with this
> compatible string.
I googled and for "acer SFA14-11" I see only "Acer Swift Air 14" names,
so that is the name people see everywhere.


Best regards,
Krzysztof

  reply	other threads:[~2026-09-28  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 10:04 [PATCH 0/3] Add support for " Jianfeng Liu
2026-09-22 10:04 ` [PATCH 1/3] dt-bindings: arm: qcom: Add " Jianfeng Liu
2026-09-28  6:39   ` Krzysztof Kozlowski
2026-09-28  8:23     ` Jianfeng Liu
2026-09-28  9:32       ` Krzysztof Kozlowski [this message]
2026-09-22 10:04 ` [PATCH 2/3] arm64: dts: " Jianfeng Liu
2026-09-22 10:04 ` [PATCH 3/3] firmware: qcom: scm: Allow QSEECOM on " Jianfeng Liu

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=0f3a7511-b191-43d6-893f-6ac70726a7c9@kernel.org \
    --to=krzk@kernel.org \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®