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
Subject: Re: [PATCH] wifi: orphan brcm80211 broadcom drivers
Date: Wed, 20 Dec 2023 18:21:36 +0200	[thread overview]
Message-ID: <87h6kcq1yn.fsf@kernel.org> (raw)
In-Reply-To: <20231220095750.307829-1-arend.vanspriel@broadcom.com> (Arend van Spriel's message of "Wed, 20 Dec 2023 10:57:50 +0100")

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

> The maintainers listed can no longer meet the expectations
> of the community. Hence changing the status to Orphan.
>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> ---
> When joining Broadcom 13 years ago and assigned to work on
> upstreaming our wifi drivers it was a fun job. Getting it
> in shape to remedy John Linville's eye-ball cancer from the
> first look at it and adding stuff after getting it out of
> staging with Greg's blessing. Setting up a Jenkins CI rig to
> nightly test the chips we support. Refactoring the driver to
> pave the road for new features.
>
> Those days it was backed up by the company because there were
> paying customers demanding it. When that support ended I decided
> to hang on and play my role as a maintainer because I cared and
> could not let go. That was probably a mistake from which I can
> only learn. Hopefully I can stay involved as a valued reviewer,
> but I somehow doubt that. Too much emotions stir that I need to
> vent, but it would only put more oil on this stupid flame war.

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.

Your mail made me think a lot about what has happened over the ~15 years
I have been involved with wireless. And this is not fun anymore, this is
more like a business with requirements and demands coming from
everywhere.

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

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

  reply	other threads:[~2023-12-20 16:21 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 [this message]
2023-12-23 20:20   ` Arend van Spriel
2024-01-13 16:27     ` Kalle Valo
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=87h6kcq1yn.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=arend.vanspriel@broadcom.com \
    --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.