From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: ZhaoJinming <zhaojinming@uniontech.com>, baochen.qiang@oss.qualcomm.com
Cc: ath11k@lists.infradead.org, jjohnson@kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v6] wifi: ath11k: fix resource leak on error in ext IRQ setup
Date: Mon, 27 Jul 2026 08:47:17 -0700 [thread overview]
Message-ID: <81a72170-870a-47be-930d-0772b7934ab2@oss.qualcomm.com> (raw)
In-Reply-To: <20260727065500.3827035-1-zhaojinming@uniontech.com>
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
next prev parent reply other threads:[~2026-07-27 15:47 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 [this message]
2026-07-28 1:45 ` 赵金明
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=81a72170-870a-47be-930d-0772b7934ab2@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zhaojinming@uniontech.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
all inboxes | Powered by JetHome®