From: 赵金明 <zhaojinming@uniontech.com>
To: "Jeff Johnson" <jeff.johnson@oss.qualcomm.com>,
baochen.qiang <baochen.qiang@oss.qualcomm.com>
Cc: ath11k <ath11k@lists.infradead.org>,
jjohnson <jjohnson@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v6] wifi: ath11k: fix resource leak on error in ext IRQ setup
Date: Tue, 28 Jul 2026 09:45:02 +0800 [thread overview]
Message-ID: <A77EF7332E024D0E+202607280945015602200@uniontech.com> (raw)
In-Reply-To: <81a72170-870a-47be-930d-0772b7934ab2@oss.qualcomm.com>
Hi Jeff,
Thank you for the reminder, and I apologize for the continued misstep.
I do remember your previous instruction about starting new patch series as separate threads. The reason I sent this v6 as a threaded reply this time was to keep the review context easily accessible in my mail client ― I find it helpful to have the feedback and the new version grouped together for side?by?side reference during the review process.
That said, I fully understand that this convenience for myself creates inconvenience for others, especially for those who use threaded views to track patch flow. My intent was to send the final, ready?to?merge version as a new thread once the review on this round had settled ― but I should have followed the established process from the start.
To correct this, I will send v7 as a completely new thread, with the link to this discussion added at the end of the commit message for traceability.
Again, sorry for the noise, and thanks for your patience.
Best regards,
Zhao Jinming
>After v4 I reminded you:
>>In the future please post new versions of patches as a separate thread.
>
>Yet once again you sent a new patch as a threaded reply instead of as a new
>thread.
>
>:(
>
>You are ruining your reputation.
>
>/jeff
>
prev parent reply other threads:[~2026-07-28 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 1:38 [PATCH v5] " ZhaoJinming
2026-07-23 1:55 ` Baochen Qiang
2026-07-25 1:44 ` Jeff Johnson
2026-07-25 2:13 ` Jeff Johnson
2026-07-27 6:55 ` [PATCH v6] " ZhaoJinming
2026-07-27 11:03 ` Rameshkumar Sundaram
2026-07-27 15:47 ` Jeff Johnson
2026-07-28 1:45 ` 赵金明 [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=A77EF7332E024D0E+202607280945015602200@uniontech.com \
--to=zhaojinming@uniontech.com \
--cc=ath11k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.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
all inboxes | Powered by JetHome®