public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Lucid Duck <lucid_duck@justthetip.ca>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
	"morrownr@gmail.com" <morrownr@gmail.com>
Subject: RE: [PATCH v4] wifi: rtw89: usb: fix TX flow control by tracking in-flight URBs
Date: Mon, 30 Mar 2026 00:42:34 +0000	[thread overview]
Message-ID: <9587a4a860d149f0932be459358085b5@realtek.com> (raw)
In-Reply-To: <5c6bb05e4e684fa3adb56ad6e9cda98d@realtek.com>

Hi Johannes,

Ping-Ke Shih wrote:
> 
> Lucid Duck <lucid_duck@justthetip.ca> wrote:
> >  usb.c | 20 ++++++++++++++++++--
> >  usb.h |  3 +++
> >  2 files changed, 21 insertions(+), 2 deletions(-)
> >
> > diff --git a/usb.c b/usb.c
> > index eb489df..6f57788 100644
> > --- a/usb.c
> > +++ b/usb.c
> 
> You must use kernel tree to send this patch as before.

Because of Lucid's mistake, patchwork assigns this patch to you, but
I think I can just assign back to me and change its state. Just a note.

Ping-Ke


  reply	other threads:[~2026-03-30  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 23:33 [PATCH v3] wifi: rtw89: usb: fix TX flow control by tracking in-flight URBs Lucid Duck
2026-03-24  0:46 ` Ping-Ke Shih
2026-03-27 19:40 ` [PATCH v4] " Lucid Duck
     [not found] ` <202603281411.62SEBByK43790225@rtits1.realtek.com.tw>
2026-03-30  0:38   ` Ping-Ke Shih
2026-03-30  0:42     ` Ping-Ke Shih [this message]
2026-03-30  2:59 ` [PATCH v5] " Lucid Duck
2026-03-30  5:35   ` Ping-Ke Shih

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=9587a4a860d149f0932be459358085b5@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lucid_duck@justthetip.ca \
    --cc=morrownr@gmail.com \
    --cc=rtl8821cerfe2@gmail.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