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,
	Fernando Piacente <nandopiacente@gmail.com>,
	Paolo Perego <pperego@suse.de>,
	Sreekanth <chvsreekanth@gmail.com>,
	Eric Curtin <ecurtin@redhat.com>
Subject: Re: [PATCH] wifi: orphan brcm80211 broadcom drivers
Date: Sat, 13 Jan 2024 18:27:09 +0200	[thread overview]
Message-ID: <87r0il8ahu.fsf@kernel.org> (raw)
In-Reply-To: <ec670eed-cd63-470c-b37b-76925a1ec6d5@broadcom.com> (Arend van Spriel's message of "Sat, 23 Dec 2023 21:20:21 +0100")

(sorry for the really late reply, I was on a long vacation)

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

> On 12/20/2023 5:21 PM, Kalle Valo wrote:
>
>> I am so sad about this but I fully understand your decision. You have
>> the best knowledge of Broadcom devices and you were involved with
>> brcm80211 from the beginning. I can guess how difficult lately it has
>> been for you to find time for upstream work but even still you
>> replied to my mails and tried to support the community the best you
>> can, which I appreciated so much. Everyone else in the corporate
>> world usually just ignore, you did not do that.
>
> Hi Kalle,
>
> Maybe I should reconsider, because it feels a bit like high school and
> the bullies won. I agreed that I can not meet expectations and the
> main aspect being testing patch series on fair amount of devices.

Yes, please reconsider! I didn't apply your patch because I was hoping I
could still convince you to continue maintaining it :)

I fully understand the challenges of maintaining a huge driver like
brcm80211: no proper documentation available, several companies
involved, a plethora of firmware branches which might work a bit
different and so many hardware variants.

> Do you think we can address that with some help? For instance by
> reaching out to several people in the community that use brcmfmac and
> ask them if they are willing to regularly test on wireless-testing. My
> experience with community members is not so great as they tend to
> loose interest and move on, but it may be worth a try. Let me know
> what you think.

I definitely think that getting a small community around brcm80211 would
be beneficial. For example, a good start would be to create a dedicated
list for brcm80211 where people can discuss about anything from testing
to developing patches and all between. lists.infradead.org is one good
place and there's also lists.linux.dev.

Let me know if there's anything I can help with. I have also CCed people
who expressed interest in helping brcm80211 development before the
holidays.

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

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

  reply	other threads:[~2024-01-13 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  9:57 [PATCH] wifi: orphan brcm80211 broadcom drivers Arend van Spriel
2023-12-20 16:21 ` Kalle Valo
2023-12-23 20:20   ` Arend van Spriel
2024-01-13 16:27     ` Kalle Valo [this message]
2024-01-13 19:11       ` Eric Curtin

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=87r0il8ahu.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=chvsreekanth@gmail.com \
    --cc=ecurtin@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nandopiacente@gmail.com \
    --cc=pperego@suse.de \
    /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.