All of lore.kernel.org
 help / color / mirror / Atom feed
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
Date: Fri, 26 Jan 2024 14:31:41 +0200	[thread overview]
Message-ID: <8734ukz36a.fsf@kernel.org> (raw)
In-Reply-To: <20240126105724.384063-1-arend.vanspriel@broadcom.com> (Arend van Spriel's message of "Fri, 26 Jan 2024 11:57:24 +0100")

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

  reply	other threads:[~2024-01-26 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 10:57 [PATCH v3] wifi: cleanup brcm80211 drivers maintainer entry Arend van Spriel
2024-01-26 12:31 ` Kalle Valo [this message]
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=8734ukz36a.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --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.