Arend Van Spriel <aspriel@xxxxxxxxx> writes:
>>> I think it's pretty safe to say that this driver is nearly
>>> unmaintained by Broadcom, definitely unmaintained by Cypress /
>>> Infineon and Arend is unable to answer questions relating to anything
>>> beyond the code as-written.
>>>
>>> Kalle, should this driver get orphaned?
>> We definitely need to consider that but let's first wait for Arend
>> to
>> comment.
>
> Using my personal email account to comment. Broadcom has pulled away
> most resources from the brcm80211 drivers as there is no business
> interest for it and it turned into a one-fifth man show as I was
> granted to work one day a week on brcm80211. Nice theory but in
> practice other work always takes priority.
Sorry to hear that. I know big corporations well enough that it doesn't
work like that in reality :/
> So "nearly unmaintained" is no exaggeration. I probably can not meet
> the expectations some people in the community have regarding driver
> maintainers, but I can still review patch submissions although I
> should keep a better eye on the list to do that. It would not be my
> choice to abandon brcm80211, but if my contributions are considered
> insufficient than I will accept that fact.
I definitely would want you to continue maintaining brcm80211! I know
how difficult it can be between a rock and a hard place so I value your
contributions, and understand sometimes you are not able to react
quickly (or at all).
What about Franky and Hante? I wonder if we should remove them? Or
convert them to reviewers?
Also I'm thinking should we change the driver status to Odd Fixes:
Odd Fixes: It has a maintainer but they don't have time to do
much other than throw the odd patch in. See below..
Of course there's no practical difference what the driver status is but
I nowadays try to keep the maintainers file up-to-date.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
