From: Jingzhou Zhu <newwheatzjz@zohomail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, 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 v6 2/2] arm64: dts: qcom: Add support for Huawei MateBook E 2019
Date: Mon, 13 Oct 2025 08:08:09 +0800 [thread overview]
Message-ID: <12758617.O9o76ZdvQC@debian-vmware> (raw)
In-Reply-To: <f03e0223-2722-4d5f-897b-91209b6c12fe@oss.qualcomm.com>
On Saturday, 11 October 2025 01:29:08 CST, Konrad Dybcio wrote:
> On 10/10/25 4:52 PM, Jingzhou Zhu wrote:
> > On Thursday, 9 October 2025 21:58:29 CST, Konrad Dybcio wrote:
> >> Please refrain from resending if it's just to apply tags, maintainer
> >> tools do it for you
> >>
> >> Konrad
> >
> > Understood. This is my first time to send patches, so I'm not very familiar
> > with the tools. Should I wait for the maintainer to pick it up, or is there
> > anything else I should do?
>
> I suppose I didn't answer your question fully in the other email.
>
> TLDR: you're good to go, it should be merged in a week or so
>
> Konrad
>
Fully understood now. Thank you for the information!
Jingzhou Zhu
next prev parent reply other threads:[~2025-10-13 0:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 13:00 [PATCH v6 0/2] arm64: dts: qcom: Introduce Huawei MateBook E 2019 Jingzhou Zhu
2025-10-08 13:00 ` [PATCH v6 1/2] dt-bindings: arm: qcom: Document " Jingzhou Zhu
2025-10-08 13:00 ` [PATCH v6 2/2] arm64: dts: qcom: Add support for " Jingzhou Zhu
2025-10-09 12:41 ` Konrad Dybcio
2025-10-09 13:49 ` Jingzhou Zhu
2025-10-09 13:58 ` Konrad Dybcio
2025-10-10 14:52 ` Jingzhou Zhu
2025-10-10 17:28 ` Konrad Dybcio
2025-10-10 17:29 ` Konrad Dybcio
2025-10-13 0:08 ` Jingzhou Zhu [this message]
2025-10-27 22:37 ` [PATCH v6 0/2] arm64: dts: qcom: Introduce " Bjorn Andersson
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=12758617.O9o76ZdvQC@debian-vmware \
--to=newwheatzjz@zohomail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).