From: Jingzhou Zhu <newwheatzjz@zohomail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@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 v3 2/2] arm64: dts: qcom: Add support for Huawei MateBook E 2019
Date: Sat, 04 Oct 2025 19:53:13 +0800 [thread overview]
Message-ID: <5021717.GXAFRqVoOG@debian-vmware> (raw)
In-Reply-To: <pbrrkfjrqoyj4qspdrordksfueyqejxcsz2oxqctczeoll6ywn@ixpaa6v4mwlv>
On Saturday, 4 October 2025 06:33:27 CST, Dmitry Baryshkov wrote:
> Did you post the board data to the ath10k@ mailing list?
>
> See https://wireless.docs.kernel.org/en/latest/en/users/drivers/ath10k/boardfiles.html
Hi, I submitted the board file several days ago (see [1]), but there's no reply from the reviewers.
Is there anything wrong with my post? It's my first time to send patches, plz let me know if I did
anything wrong, thanks!
[1] https://lists.infradead.org/pipermail/ath10k/2025-September/016495.html
next prev parent reply other threads:[~2025-10-04 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 14:21 [PATCH v2 0/2] arm64: dts: qcom: Introduce Huawei MateBook E 2019 Jingzhou Zhu
2025-10-01 14:21 ` [PATCH v2 1/2] dt-bindings: arm: qcom: Document " Jingzhou Zhu
2025-10-01 14:21 ` [PATCH v2 2/2] arm64: dts: qcom: Add support for " Jingzhou Zhu
2025-10-02 3:27 ` Bjorn Andersson
2025-10-03 13:19 ` [PATCH v3 0/2] arm64: dts: qcom: Introduce " Jingzhou Zhu
2025-10-03 13:19 ` [PATCH v3 1/2] dt-bindings: arm: qcom: Document " Jingzhou Zhu
2025-10-03 13:19 ` [PATCH v3 2/2] arm64: dts: qcom: Add support for " Jingzhou Zhu
2025-10-03 22:33 ` Dmitry Baryshkov
2025-10-04 11:53 ` Jingzhou Zhu [this message]
2025-10-05 22:05 ` Dmitry Baryshkov
2025-10-03 21:57 ` [PATCH v3 0/2] arm64: dts: qcom: Introduce " Dmitry Baryshkov
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=5021717.GXAFRqVoOG@debian-vmware \
--to=newwheatzjz@zohomail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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).