From: Alastair D'Silva <alastair@d-silva.org>
To: Luka Gejak <luka.gejak@linux.dev>,
Ping-Ke Shih <pkshih@realtek.com>,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@kernel.org>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Ulf Hansson <ulfh@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH rtw-next v9 0/4] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm
Date: Tue, 10 Nov 2026 07:29:38 +1100 [thread overview]
Message-ID: <23518740c620e5575d5ca5f46aa99f1dbb7e1172.camel@d-silva.org> (raw)
In-Reply-To: <162821b6cf0e6d17aa33c81d55a716b553e70579@linux.dev>
On Sun, 2026-11-08 at 06:06 +0000, Luka Gejak wrote:
>
> > Please take Luka's Reviewed-by for each patch, and send v10.
> >
> > [1] https://patchwork.kernel.org/project/linux-
> > wireless/list/?series=&submitter=Alastair&state=*&q=&archive=&delegate=
> >
>
> It might be the same issue lore is experiencing. Nothing newer than
> November 6th is appearing, maybe it's related?
>
>
Looks like it's still stuck on 6th of November - is there someone we can poke?
--
Alastair D'Silva
0493 18 5566
prev parent reply other threads:[~2026-11-09 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 3:53 Alastair D'Silva
2026-11-07 3:53 ` [PATCH rtw-next v9 1/4] wifi: rtw88: sdio: Handle allocation and read errors in rtw_sdio_rxfifo_recv Alastair D'Silva
2026-11-07 3:53 ` [PATCH rtw-next v9 2/4] wifi: rtw88: sdio: Track running state and cancel TX worker on stop Alastair D'Silva
2026-11-07 3:53 ` [PATCH rtw-next v9 3/4] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm Alastair D'Silva
2026-11-07 3:53 ` [PATCH rtw-next v9 4/4] wifi: rtw88: sdio: Split rtw_sdio_rx_isr into 8051 and 3081 variants Alastair D'Silva
2026-11-07 8:32 ` [PATCH rtw-next v9 0/4] wifi: rtw88: sdio: Fix unhandled RX request interrupt storm Luka Gejak
2026-11-08 3:06 ` Ping-Ke Shih
2026-11-08 6:06 ` Luka Gejak
2026-11-09 20:29 ` Alastair D'Silva [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=23518740c620e5575d5ca5f46aa99f1dbb7e1172.camel@d-silva.org \
--to=alastair@d-silva.org \
--cc=jernej.skrabec@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luka.gejak@linux.dev \
--cc=martin.blumenstingl@googlemail.com \
--cc=pkshih@realtek.com \
--cc=ulfh@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®