From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@kernel.org>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend.vanspriel@broadcom.com>,
brcm80211@lists.linux.dev
Subject: [PATCH v3] wifi: cleanup brcm80211 drivers maintainer entry
Date: Fri, 26 Jan 2024 11:57:24 +0100 [thread overview]
Message-ID: <20240126105724.384063-1-arend.vanspriel@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]
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>
The driver wireless wiki can also use a cleanup. Probably will add
a list of people who volunteer to perform regression testing with
the chipsets they have available.
Hope we can move on in a relatively fresh new year and leave the
frustration behind us.
This patch was based on the wireless tree, but it probably applies
to wireless-next as well. I am fine either way.
Regards,
Arend
[1] https://lore.kernel.org/linux-wireless/20231107-brcmfmac-wpa3-v1-1-4c7db8636680@marcan.st/
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d8ca0e10c8d1..25d530ab90d7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4169,14 +4169,14 @@ F: drivers/firmware/broadcom/tee_bnxt_fw.c
F: drivers/net/ethernet/broadcom/bnxt/
F: include/linux/firmware/broadcom/tee_bnxt_fw.h
-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>
+BROADCOM BRCM80211 IEEE802.11 WIRELESS DRIVERS
+M: Arend van Spriel <arend.vanspriel@broadcom.com>
L: linux-wireless@vger.kernel.org
+L: brcm80211@lists.linux.dev
L: brcm80211-dev-list.pdl@broadcom.com
S: Supported
F: drivers/net/wireless/broadcom/brcm80211/
+F: include/linux/platform_data/brcmfmac.h
BROADCOM BRCMSTB GPIO DRIVER
M: Doug Berger <opendmb@gmail.com>
base-commit: 1b023d475ae928f3036cefee9ea0a499af1d8900
--
2.32.0
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next reply other threads:[~2024-01-26 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 10:57 Arend van Spriel [this message]
2024-01-26 12:31 ` [PATCH v3] wifi: cleanup brcm80211 drivers maintainer entry Kalle Valo
2024-01-29 16:29 ` [v3] MAINTAINERS: wifi: brcm80211: cleanup entry Kalle Valo
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=20240126105724.384063-1-arend.vanspriel@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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.