From: Devin Wittmayer <lucid_duck@justthetip.ca>
To: stable@vger.kernel.org
Cc: Felix Fietkau <nbd@nbd.name>,
Wentao Guan <guanwentao@uniontech.com>,
linux-wireless@vger.kernel.org
Subject: [PATCH 0/6] wifi: mt76: mt7925: cancel mlo_pm_work at teardown
Date: Wed, 9 Sep 2026 20:11:00 -0700 [thread overview]
Message-ID: <20260910031106.25906-1-lucid_duck@justthetip.ca> (raw)
These two are marked for stable and were not picked up:
81faf578320d ("wifi: mt76: mt7925: cancel mlo_pm_work on stop")
2889e84282dd ("wifi: mt76: mt7925: cancel pending mlo_pm_work")
The second is Wentao's and catches five paths that mine did not, so
thank you for that.
They reached mainline on 31 July and first ship in 7.3. Neither applies
to 6.18.y, 7.1.y or 7.2.y, so backports for all three follow, two per
tree. Each applies cleanly and builds with no new warnings.
On a multi-link connection the driver schedules a job five seconds out
while setting up power saving. Nothing cancelled it when the device went
away, so a removal inside that window leaves the job to fire afterwards.
The code has been in every release since 6.15.
next reply other threads:[~2026-09-10 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 3:11 Devin Wittmayer [this message]
2026-09-10 3:11 ` [PATCH 6.18.y 1/2] wifi: mt76: mt7925: cancel mlo_pm_work on stop Devin Wittmayer
2026-09-10 3:11 ` [PATCH 6.18.y 2/2] wifi: mt76: mt7925: cancel pending mlo_pm_work Devin Wittmayer
2026-09-10 3:11 ` [PATCH 7.1.y 1/2] wifi: mt76: mt7925: cancel mlo_pm_work on stop Devin Wittmayer
2026-09-10 3:11 ` [PATCH 7.1.y 2/2] wifi: mt76: mt7925: cancel pending mlo_pm_work Devin Wittmayer
2026-09-10 3:11 ` [PATCH 7.2.y 1/2] wifi: mt76: mt7925: cancel mlo_pm_work on stop Devin Wittmayer
2026-09-10 3:11 ` [PATCH 7.2.y 2/2] wifi: mt76: mt7925: cancel pending mlo_pm_work Devin Wittmayer
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=20260910031106.25906-1-lucid_duck@justthetip.ca \
--to=lucid_duck@justthetip.ca \
--cc=guanwentao@uniontech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=stable@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