From: Krzysztof Kozlowski <krzk@kernel.org>
To: weifu wu <wwfu06@163.com>, andersson@kernel.org, konradybcio@kernel.org
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add Acer Swift SFA14-11 DT and bindings
Date: Mon, 5 Jan 2026 11:29:54 +0100 [thread overview]
Message-ID: <5c1e12f4-5de1-489f-ac15-9ac18aeb1488@kernel.org> (raw)
In-Reply-To: <20260105101239.2591419-1-wwfu06@163.com>
On 05/01/2026 11:12, weifu wu wrote:
> This series adds initial device tree support for the Acer Swift SFA14-11 laptop based on the Qualcomm X1E78100 SoC.
>
> Patch 1 introduces the DT binding documentation for the new board compatible string.
> Patch 2 adds the device tree source file and updates the Makefile to include it.
>
> The device tree enables basic peripherals including the eDP panel, backlight, USB and PCIe.
> The changes have been tested by building dtbs and booting on the target hardware, with display and backlight verified via eDP.
>
> The first attempt to submit the patch failed due to an SMTP server error. The patch is being resubmitted with a different SMTP server configured.
You already sent it and received reply. So one day later, you read the
review, decided to ignore everything else I wrote except the threading
and sent exactly the same. So what about my time spent on reviewing
this? Does not matter? If so, NAK.
Read submitting patches also how to properly write commit msgs.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-01-05 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 10:12 [PATCH 0/2] Add Acer Swift SFA14-11 DT and bindings weifu wu
2026-01-05 10:12 ` [PATCH 1/2] dt-bindings: arm: qcom: add Acer Swift SFA14-11 weifu wu
2026-01-05 10:27 ` Krzysztof Kozlowski
2026-01-05 10:12 ` [PATCH 2/2] arm64: dts: qcom: add Acer Swift SFA14-11 device tree weifu wu
2026-01-05 10:27 ` Krzysztof Kozlowski
2026-01-05 10:29 ` Krzysztof Kozlowski [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=5c1e12f4-5de1-489f-ac15-9ac18aeb1488@kernel.org \
--to=krzk@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=robh@kernel.org \
--cc=wwfu06@163.com \
/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