From: Goliath Zhu <goliath.zhu@clipsneko.cc>
To: linux-wireless@vger.kernel.org
Cc: nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, sean.wang@mediatek.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, goliath.zhu@clipsneko.cc
Subject: [PATCH 0/2] wifi: mt76: fix RX NAPI teardown on mt7996 removal
Date: Fri, 17 Jul 2026 11:00:08 +0000 [thread overview]
Message-ID: <0106019f6fbbd2b3-deb608fb-9fee-4026-98b5-5b108c95e4af-000000@ap-northeast-1.amazonses.com> (raw)
Fix two RX NAPI teardown issues in the mt7996 removal path.
The first patch disables the RX NAPI instances before the common DMA
cleanup deletes them. This is the RX counterpart of commit 78ab4be54953
("wifi: mt76: disable napi on driver removal"), which fixed the same
warning for TX NAPI.
The second patch fixes a regression introduced by commit 6b470f36616e
("wifi: mt76: Fix memory leak destroying device"). Keep visiting WED RRO
queues to release their page pools, but do not delete NAPI instances
which were never registered while WED is active.
Build-tested with CONFIG_MT7996E=m, CONFIG_NET_MEDIATEK_SOC_WED=y and
W=1.
Goliath Zhu (2):
wifi: mt76: mt7996: disable RX NAPI on driver removal
wifi: mt76: skip NAPI deletion for WED RRO queues
drivers/net/wireless/mediatek/mt76/dma.c | 4 +++-
drivers/net/wireless/mediatek/mt76/mt7996/init.c | 11 +++++++++++
2 files changed, 14 insertions(+), 1 deletion(-)
base-commit: 58717b2a1365d06c8c64b72aa948541b53fe31eb
--
2.55.0
reply other threads:[~2026-07-17 11:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0106019f6fbbd2b3-deb608fb-9fee-4026-98b5-5b108c95e4af-000000@ap-northeast-1.amazonses.com \
--to=goliath.zhu@clipsneko.cc \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.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