All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Arend Van Spriel <aspriel@gmail.com>
Cc: Julian Calaby <julian.calaby@gmail.com>,
	Dmitry Antipov <dmantipov@yandex.ru>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
	Franky Lin <franky.lin@broadcom.com>,
	Hante Meuleman <hante.meuleman@broadcom.com>,
	Hector Martin <marcan@marcan.st>,
	SHA-cyfmac-dev-list@infineon.com,
	brcm80211-dev-list.pdl@broadcom.com
Subject: Re: On brcm80211 maintenance and support
Date: Wed, 11 Oct 2023 10:46:36 +0300	[thread overview]
Message-ID: <87mswpfvoj.fsf@kernel.org> (raw)
In-Reply-To: <cd9e71c8-2884-427a-a394-756f62ab09ba@gmail.com> (Arend Van Spriel's message of "Mon, 9 Oct 2023 22:22:23 +0200")

Arend Van Spriel <aspriel@gmail.com> 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

      parent reply	other threads:[~2023-10-11  7:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 13:37 On brcm80211 maintenance and support Dmitry Antipov
2023-10-06 10:44 ` Julian Calaby
2023-10-06 12:21   ` Kalle Valo
2023-10-06 15:34     ` Hector Martin
2023-10-06 15:48       ` Dmitry Antipov
2023-10-07 12:50         ` Hector Martin
2023-10-10 14:52           ` Neal Gompa
2023-10-10 15:35             ` Phil Elwell
2023-10-11 10:32               ` Kalle Valo
2023-10-11 10:45                 ` Phil Elwell
2023-10-11 10:23             ` Kalle Valo
2023-10-11 11:28               ` Hector Martin
2023-10-11 11:47                 ` Phil Elwell
2023-10-12  8:41                 ` Arend van Spriel
2023-10-12 16:25                   ` Florian Fainelli
2023-10-09 20:22     ` Arend Van Spriel
2023-10-10 14:57       ` Hector Martin
2023-10-11  7:46       ` Kalle Valo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mswpfvoj.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=SHA-cyfmac-dev-list@infineon.com \
    --cc=aspriel@gmail.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=dmantipov@yandex.ru \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=marcan@marcan.st \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.