From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Jiale Yao <yaojiale02@163.com>,
Jeff Johnson <jjohnson@kernel.org>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Shayne Chen <shayne.chen@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Ilan Peer <ilan.peer@intel.com>,
Gregory Greenman <gregory.greenman@intel.com>,
Deren Wu <deren.wu@mediatek.com>,
Ming Yen Hsieh <mingyen.hsieh@mediatek.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/4] wifi: unwind failed interface setup and recovery
Date: Wed, 28 Oct 2026 08:01:40 -0700 [thread overview]
Message-ID: <d094dc46-760d-4ee5-9404-9fa73a16a6bf@oss.qualcomm.com> (raw)
In-Reply-To: <20261028050337.127464-1-yaojiale02@163.com>
On 10/27/2026 10:03 PM, Jiale Yao wrote:
> Several wireless interface setup and reset recovery paths publish host
> pointers or create firmware state before later operations which can fail.
> Their error paths either retain pointers to vifs that mac80211 will free
> or continue after firmware interface restoration has failed.
>
> Clear the published ath10k and iwlwifi pointers on add failure. Check the
> mt7921 and mt7925 firmware restore results, remove partial state and stop
> configuring the affected interface. Each patch fixes an independent
> driver path and can be applied separately.
>
> Jiale Yao (4):
> wifi: ath10k: clear monitor interface after add failure
> wifi: iwlwifi: mvm: clear P2P device pointer on add failure
> wifi: mt76: mt7921: unwind interface restore failures
> wifi: mt76: mt7925: unwind link restore failures
>
> drivers/net/wireless/ath/ath10k/mac.c | 1 +
> .../wireless/intel/iwlwifi/mvm/mld-mac80211.c | 5 +++-
> .../net/wireless/mediatek/mt76/mt7921/mac.c | 16 +++++++++---
> .../net/wireless/mediatek/mt76/mt7925/mac.c | 26 ++++++++++++++++---
> 4 files changed, 41 insertions(+), 7 deletions(-)
>
You are sending patches that fall into 3 different maintainer trees in one series.
It is much easier for us maintainers if you split your patches by maintainer.
/jeff
prev parent reply other threads:[~2026-10-28 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 5:03 [PATCH 0/4] wifi: unwind failed interface setup and recovery Jiale Yao
2026-10-28 5:03 ` [PATCH 3/4] wifi: mt76: mt7921: unwind interface restore failures Jiale Yao
2026-10-28 5:03 ` [PATCH 4/4] wifi: mt76: mt7925: unwind link " Jiale Yao
2026-10-28 15:01 ` Jeff Johnson [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=d094dc46-760d-4ee5-9404-9fa73a16a6bf@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ath10k@lists.infradead.org \
--cc=deren.wu@mediatek.com \
--cc=gregory.greenman@intel.com \
--cc=ilan.peer@intel.com \
--cc=jjohnson@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mingyen.hsieh@mediatek.com \
--cc=miriam.rachel.korenblit@intel.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=yaojiale02@163.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