[PATCH 00/16] hostapd: scale up MLO flows

[Jouni Malinen]

On Wed, Mar 06, 2024 at 11:09:31PM +0530, Aditya Kumar Singh wrote:
> This series extends the basic MLO support to properly create/handle/remove
> MLD links. At the same time, it also makes the code flow scalable to later
> support multiple co-hosted MLDs as well various other features.
> 
> Aditya Kumar Singh (15):
>   tests: MLD: remove mld_id config
>   hostapd: MLO: add separate MLD level structure
>   hostapd: MLO: use MLD struct for MLD level info
>   hostapd: MLO: assign link ID during BSS creation
>   hostapd: MLO: clean up MLD when not required any further
>   hostapd: MLO: cache hostapd_data context in per link bss struct
>   hostapd: MLO: remove redundant put_freq call in set_ap
>   hostapd: MLO: re-factor nl80211_remove_links() function
>   hostpad: MLO: nl80211: remove links while removing the interface
>   hostapd: MLO: add support to remove the link before removing interface
>   hostapd: MLO: refresh other iface beacons when one iface gets
>     disabled/enabled
>   hostapd: MLO: fix advertisement of MLD capabilities
>   hostapd: MLO: de-initialize/disable link BSS properly
>   hostapd: MLD: add support to remove link station from AP
>   hostapd: MLD: remove restriction of disabling first link bss at last
> 
> Sriram R (1):
>   hostapd: MLO: avoid usage of mld_id as user configuration

Thanks, applied with cleanup.

PS.

Whenever the commit message would include something like "While at it,
lets do this other things", that is most likely a good indication that
the patch should be split into two where that "while at it" part is in
the second patch.. In particular, whenever refactoring functions, no
functionality changes should be included in the patch. Those will just
add more work for me to revert things partially to figure out what
exactly happen and to confirm that refactoring was done correctly before
being able to apply the patch.

-- 
Jouni Malinen                                            PGP id EFC895FA