From: Hector Martin <marcan@marcan.st>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
SHA-cyfmac-dev-list@infineon.com,
brcm80211-dev-list.pdl@broadcom.com,
Asahi Linux <asahi@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Kalle Valo <kvalo@kernel.org>,
Julian Calaby <julian.calaby@gmail.com>
Subject: Re: On brcm80211 maintenance and support
Date: Sat, 7 Oct 2023 21:50:56 +0900 [thread overview]
Message-ID: <e470902a-35eb-9bb4-7a9e-167f985c98bb@marcan.st> (raw)
In-Reply-To: <e1ee4d76-f717-a67c-8099-7b91192ba1ca@yandex.ru>
On 07/10/2023 00.48, Dmitry Antipov wrote:
> On 10/6/23 18:34, Hector Martin wrote:
>
>> For better or worse, if nobody else does, I'm willing to sign up to
>> maintain the chips shipping on Apple ARM64 machines (i.e. BCM4378,
>> BCM4387, BCM4388 - that last one I have bringup for downstream, just got
>> it done this week) and partially BCM4377 as a bonus (since I have access
>> to an older Intel Mac with that one, and already did bringup for it,
>> though my access is sporadic). I'm already playing part time maintainer
>> anyway (other folks have already sent us patches I'll have to upstream),
>> and we need this driver to keep working and continue to support new chips.
>
> Good news. Would you capable to consider some generic (not hooked to any
> particular hardware) things like [1] ?
>
> [1] https://lore.kernel.org/linux-wireless/20230703162458.155942-1-dmantipov@yandex.ru/
>
Sure, I've done cleanup type stuff myself too.
- Hector
next prev parent reply other threads:[~2023-10-07 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f78e624-62ee-3ae5-1db4-a0411566def8@yandex.ru>
[not found] ` <CAGRGNgU7aySyUny9aG_+wXiKJ7j1weosa-rZDY4_WAXbq-3ABg@mail.gmail.com>
[not found] ` <87ttr454bh.fsf@kernel.org>
2023-10-06 15:34 ` Hector Martin
2023-10-06 15:48 ` Dmitry Antipov
2023-10-07 12:50 ` Hector Martin [this message]
2023-10-10 14:52 ` Neal Gompa
2023-10-10 15:35 ` Phil Elwell
2023-10-11 10:32 ` Kalle Valo
2023-10-11 10:45 ` Phil Elwell
2023-10-11 10:23 ` Kalle Valo
2023-10-11 11:28 ` Hector Martin
2023-10-11 11:47 ` Phil Elwell
2023-10-12 8:41 ` Arend van Spriel
2023-10-12 16:25 ` Florian Fainelli
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=e470902a-35eb-9bb4-7a9e-167f985c98bb@marcan.st \
--to=marcan@marcan.st \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=asahi@lists.linux.dev \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=dmantipov@yandex.ru \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=julian.calaby@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lvc-project@linuxtesting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®