Received-SPF: pass (google.com: domain of linux-wireless+bounces-2564-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Kalle Valo <kvalo@kernel.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,  brcm80211@lists.linux.dev
Subject: Re: [PATCH v3] wifi: cleanup brcm80211 drivers maintainer entry
References: <20240126105724.384063-1-arend.vanspriel@broadcom.com>
Date: Fri, 26 Jan 2024 14:31:41 +0200
In-Reply-To: <20240126105724.384063-1-arend.vanspriel@broadcom.com> (Arend van
	Spriel's message of "Fri, 26 Jan 2024 11:57:24 +0100")
Message-ID: <8734ukz36a.fsf@kernel.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain

Arend van Spriel <arend.vanspriel@broadcom.com> 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@lists.linux.dev
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> ---
> 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@lists.linux.dev>

Arend, thanks for creating the list. Apparently to subscribe to the list
send email to:

brcm80211+subscribe@lists.linux.dev

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