Re: linux-next: manual merge of the wireless-next tree with the origin tree

On Sun, 26 Jul 2026 12:33:13 +0200, Johannes Berg wrote:
> But because I don't think (a) we should fix that in the merge, and (b)
> it's actually very important, I'm just going to leave it as
> "notify_driver".

I traced both paths again and I agree with you. Retrying against a broken
AP is the better failure mode than confusing the driver, and the trigger
needs an AP that reports success without an AID Response element, so it is
not worth changing the merge resolution.

> If we actually observe this in practice and want to get rid of the time
> wasting, I guess we could add a path out that does both, but I'm not
> sure it's worth it.

For the record, destroy_assoc_data already does both. Since f13e573ab3f12
moved drv_mgd_complete_tx() into ieee80211_destroy_assoc_data(), that label
notifies the driver before the link is torn down, then abandons. No
additional path would be needed. The impact is negligible either way, so I
agree it is not worth touching now.

Thanks for looking at it.

Zhao