Re: [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn

[Johannes Berg <johannes@sipsolutions.net>]

Hi,

> > 2) it'd help for the automatic bot runs etc. to have, in the subject,
> >    '[PATCH wireless-next]' (or perhaps rtw-next etc.)
> 
> Oh right; that wasn't too obvious to me because get_maintainer has
> linux-wireless@ in the list but also had the brcm80211 - so I
> didn't know if this went through brcm or wireless picked it up.
> And what's rtw ?

Hmm, right, brcm80211 does have a separate list but patches still flow
only via the wireless list.

Currently, we have:
ath/ath-next - Qualcomm drivers
rtw/rtw-next - Realtek drivers
iwlwifi-fixes/iwlwifi-next - Intel iwlwifi driver
mt76 - Mediatek drivers
wireless / wireless-next - catch-all for everything else

> (Perhaps a Documenation/process/maintainer-wireless.rst would be good? )

Yeah, perhaps, though it's kind of difficult to really pin down the
exact list, it has been changing a bit.

TBH, wireless / wireless-next is mostly just fine anyway. Only if
something depends on other work in the specific trees would the other
tags really be needed, i.e. for people who work on it more actively.
With wireless / wireless-next the bot will still build-test it etc.,
whereas without a tag it may never do that at all.

johannes