Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> writes: > There has been some discussion about what is expected from > a maintainer and so a cleanup seems to be in order. A dedicated > mailing list has been created to discuss brcm80211 specific > development issues. Keeping the status as Supported although > help in maintaining this driver is welcomed. > > Cc: brcm80211@xxxxxxxxxxxxxxx > Signed-off-by: Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> > --- > changelog: > V2: let's not orphan the drivers for now > V3: switch to my Broadcom email > > The discussion around the SAE password patch [1] was a lively one > and at some point I wanted to drop the ball and be done with it. > However, when the emotions subsided and people offered to help out > with maintaining the brcm80211 drivers I decided to stay on for the > job. The discussion had some valid points specifically on my actual > involvement. Hopefully I can improve in that aspect. I sharpened my > email filters to keep better eye on brcm80211 related queryies, > patches and what not. > > Another step taken is the creation of a specific mailing list for > brcm80211 development topics: > > <brcm80211@xxxxxxxxxxxxxxx> Arend, thanks for creating the list. Apparently to subscribe to the list send email to: brcm80211+subscribe@xxxxxxxxxxxxxxx Though I didn't get any reply yet, hopefully it's just slow. > This patch was based on the wireless tree, but it probably applies > to wireless-next as well. I am fine either way. We usually take patches to MAINTAINERS file to wireless, less conflicts that way. So I'll queue this to wireless. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
