From: Hongyang Zhao <hongyang.zhao@thundersoft.com>
To: krzk@kernel.org
Cc: andersson@kernel.org, casey.connolly@linaro.org,
christopher.obbard@linaro.org, hongyang.zhao@thundersoft.com,
linux-arm-msm@vger.kernel.org, loic.minier@oss.qualcomm.com
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts
Date: Thu, 9 Oct 2025 19:05:10 +0800 [thread overview]
Message-ID: <20251009110510.23698-1-hongyang.zhao@thundersoft.com> (raw)
In-Reply-To: <92e387fe-9481-485b-ba1e-7eb6d520dc77@kernel.org>
> On 30/09/2025 13:32, Hongyang Zhao wrote:
> > Add binding for the Thundercomm RUBIK Pi 3 board,
> > which is based on the Qualcomm Dragonwing QCS6490 SoC.
> >
> > Signed-off-by: Hongyang Zhao <hongyang.zhao@thundersoft.com>
>
> <form letter>
> Please use scripts/get_maintainers.pl to get a list of necessary people
> and lists to CC. It might happen, that command when run on an older
> kernel, gives you outdated entries. Therefore please be sure you base
> your patches on recent Linux kernel.
>
> Tools like b4 or scripts/get_maintainer.pl provide you proper list of
> people, so fix your workflow. Tools might also fail if you work on some
> ancient tree (don't, instead use mainline) or work on fork of kernel
> (don't, instead use mainline). Just use b4 and everything should be
> fine, although remember about `b4 prep --auto-to-cc` if you added new
> patches to the patchset.
>
> You missed at least devicetree list (maybe more), so this won't be
> tested by automated tooling. Performing review on untested code might be
> a waste of time.
>
> Please kindly resend and include all necessary To/Cc entries.
> </form letter>
>
> Best regards,
> Krzysztof
Thank you very much. Understood. I will make the adjustments and resend
the new patch. However, since the discussion on [PATCH v4 1/2] is
still ongoing, I should wait a few days before sending it.
--
Thanks,
Hongyang
prev parent reply other threads:[~2025-10-09 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 4:32 [PATCH v4 0/2] arm64: dts: qcom: rubikpi3: Add qcs6490-rubikpi3 board dts Hongyang Zhao
2025-09-30 4:32 ` [PATCH v4 1/2] " Hongyang Zhao
2025-10-06 10:33 ` Konrad Dybcio
2025-10-09 10:30 ` Hongyang Zhao
2025-10-22 16:47 ` Konrad Dybcio
2025-10-30 2:21 ` Hongyang Zhao
2025-09-30 4:32 ` [PATCH v4 2/2] dt-bindings: arm: qcom: rubikpi3: document rubikpi3 board binding Hongyang Zhao
2025-09-30 5:30 ` Dmitry Baryshkov
2025-09-30 6:26 ` Hongyang Zhao
2025-10-06 8:53 ` Krzysztof Kozlowski
2025-10-09 11:05 ` Hongyang Zhao [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=20251009110510.23698-1-hongyang.zhao@thundersoft.com \
--to=hongyang.zhao@thundersoft.com \
--cc=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=christopher.obbard@linaro.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.minier@oss.qualcomm.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