From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jingzhou Zhu <newwheatzjz@zohomail.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: Fri, 10 Oct 2025 19:28:29 +0200 [thread overview]
Message-ID: <61f77b51-af6e-4625-8d58-fee8f93e1d5e@oss.qualcomm.com> (raw)
In-Reply-To: <2386127.ElGaqSPkdT@debian-vmware>
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?
Because the current version is v6.17 (not -rc), we're in what's
deceptively called a "merge window". This is when Linus Torvalds merges
pull requests from maintainers downstream of him.
Your patches go through the trees of these maintainers, in this case:
qcom-arm64-dts via Bjorn Andersson
-> soc-arm64-dts via Arnd Bergmann
-> torvalds/master via Linus Torvalds
Maintainers generally refrain from accepting non-urgent changes until
Torvalds tags the next -rc1 release (v6.18-rc1 in this case), after
which they start picking up changes again.
After your patches are picked up, they show up in linux-next, which
is notably a release ahead of torvalds/master (i.e. it previews the
'next' release), so if your patch gets merged when 6.18-rc1 is the
newest, it will show up in v6.19.
Another note is that -rcs are tagged weekly, and maintainers are
reluctant to accept big changes at about -rc5, since they need
time for CIs, build bots and users to test.
A cycle normally includes 7-8 release candidate revisions.
Konrad
next prev parent reply other threads:[~2025-10-10 17:28 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 [this message]
2025-10-10 17:29 ` Konrad Dybcio
2025-10-13 0:08 ` Jingzhou Zhu
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=61f77b51-af6e-4625-8d58-fee8f93e1d5e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=newwheatzjz@zohomail.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;
as well as URLs for NNTP newsgroup(s).