linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Wright Feng <wright.feng@infineon.com>,
	<linux-wireless@vger.kernel.org>,
	<brcm80211-dev-list@broadcom.com>,
	<SHA-cyfmac-dev-list@infineon.com>,
	Franky Lin <franky.lin@broadcom.com>,
	Hante Meuleman <hante.meuleman@broadcom.com>
Subject: Re: [PATCH] MAINTAINERS: update maintainer list for Infineon
Date: Thu, 10 Feb 2022 16:10:42 +0200	[thread overview]
Message-ID: <87v8xm3j8d.fsf@kernel.org> (raw)
In-Reply-To: <17eb3f987f0.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (Arend Van Spriel's message of "Tue, 01 Feb 2022 07:29:42 +0100")

Arend Van Spriel <arend.vanspriel@broadcom.com> writes:

> On January 31, 2022 4:08:29 PM Kalle Valo <kvalo@kernel.org> wrote:
>
>> Wright Feng <wright.feng@infineon.com> writes:
>>
>>> From: Chi-Hsien Lin <chi-hsien.lin@infineon.com>
>>>
>>> Add new maintainer and remove old maintainers.
>>>
>>> Signed-off-by: Chi-Hsien Lin <chi-hsien.lin@infineon.com>
>>> Signed-off-by: Wright Feng <wright.feng@infineon.com>
>>> ---
>>> MAINTAINERS | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 5ebfc9de0caf..845058803f95 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -3759,9 +3759,9 @@ BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER
>>> M: Arend van Spriel <aspriel@gmail.com>
>>> M: Franky Lin <franky.lin@broadcom.com>
>>> M: Hante Meuleman <hante.meuleman@broadcom.com>
>>> -M: Chi-hsien Lin <chi-hsien.lin@infineon.com>
>>> M: Wright Feng <wright.feng@infineon.com>
>>> -M: Chung-hsien Hsu <chung-hsien.hsu@infineon.com>
>>> +M: Double Lo <double.lo@infineon.com>
>>> +M: Kurt Lee <kurt.lee@infineon.com>
>>
>> I'm not really a fan of having too many maintainers, I would say max is
>> 3 and even that needs good justification. And most importantly, is
>> anyone else than Arend even doing any maintainer work for brcmfmac and
>> brcmsmac?
>
> Guess it should be clear what falls under the term "maintainer work".

From my point of view most important tasks of a maintainer are reviewing
patches and addressessing regressions (both runtime and build issues).
Of course there are others tasks as well, but these I consider crucial.

> Infineon does a better job these days when it comes to contributions
> adding features and new chip support, but that doesn't fall under the
> category although maintainers do submit their own patches. It's good
> to have a go-to guy at Infineon as they independently work on firmware
> and it's APIs. On our side I can probably remove Hante from the list.

Anyone can submit patches, and there can be a contact person from a
company even if it's not mentioned in MAINTAINERS.

I want to see that a maintainer really cares about upstream and works
with the community, like you Arend do. I do not want to add persons to
MAINTAINERS file and never hear from them again, that's just wasting
everyone's time.

To give a positive example, Ping does a great job maintaining Realtek's
rtw88 and rtw89 drivers. So if a company wants to learn how to become a
good maintainer, follow what Ping does :)

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      reply	other threads:[~2022-02-10 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28  6:13 [PATCH] MAINTAINERS: update maintainer list for Infineon Wright Feng
2022-01-31 15:08 ` Kalle Valo
2022-02-01  6:29   ` Arend Van Spriel
2022-02-10 14:10     ` 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=87v8xm3j8d.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=SHA-cyfmac-dev-list@infineon.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wright.feng@infineon.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).