From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Hector Martin <marcan@marcan.st>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kalle Valo <kvalo@kernel.org>,
Daniel Berlin <dberlin@dberlin.org>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
SHA-cyfmac-dev-list@infineon.com, asahi@lists.linux.dev,
brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
David Airlie <airlied@redhat.com>,
Daniel Vetter <daniel@ffwll.ch>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Phil Elwell <phil@raspberrypi.com>,
Nick Hollinghurst <nick.hollinghurst@raspberrypi.com>
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password
Date: Wed, 20 Dec 2023 18:05:34 +0700 [thread overview]
Message-ID: <ZYLKftqKFJ_PMmF3@archie.me> (raw)
In-Reply-To: <6e330280-0b0a-4483-ac09-cd974d87a7ae@marcan.st>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
On Wed, Dec 20, 2023 at 01:16:20PM +0900, Hector Martin wrote:
>
>
> On 2023/12/20 10:44, Linus Torvalds wrote:
> > Put another way: if we effectively don't have a driver maintainer that
> > can test things, and somebody is willing to step up, shouldn't we take
> > that person up on it?
>
> Personally, I do think the rPi folks themselves should step up for
> *testing* at the very least. I did point them at our downstream WiFi
> branch at one point during a previous discussion and haven't heard back,
> so either they never tested it, or they did and it didn't break
> anything. If they're shipping popular Linux hardware where the WiFi
> chipset vendor has fully and completely checked out of any upstream
> support, they need to either accept that upstream support will likely
> break at some point (because that's just what happens when nobody cares
> about a given piece of hardware, especially with drivers shared across
> others like this one) or they need to proactively step up and take on,
> minimally, an early testing role themselves.
I'm agree that downstream (e.g. rPi) developers should also participating
in upstream kernel development.
Also Cc: rPi folks to solicit their opinions.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-20 11:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 6:05 [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password Hector Martin
2023-11-08 11:12 ` Neal Gompa
2023-12-17 11:25 ` Kalle Valo
2023-12-19 8:52 ` Arend Van Spriel
2023-12-19 8:57 ` Kalle Valo
2023-12-19 11:01 ` Hector Martin
2023-12-19 13:46 ` Arend van Spriel
2023-12-19 14:26 ` Julian Calaby
2023-12-21 20:39 ` Marcel Holtmann
2023-12-22 0:03 ` Neal Gompa
2023-12-22 6:16 ` Marcel Holtmann
2023-12-24 9:03 ` Arend van Spriel
[not found] ` <CAF4BwTXNtu30DAgBXo4auDaDK0iWc9Ch8f=EH+facQ-_F-oMUQ@mail.gmail.com>
2023-12-19 14:42 ` Kalle Valo
2023-12-20 0:06 ` Hector Martin
2023-12-20 1:44 ` Linus Torvalds
2023-12-20 4:16 ` Hector Martin
2023-12-20 11:05 ` Bagas Sanjaya [this message]
2023-12-20 10:20 ` Kalle Valo
2023-12-20 15:55 ` Kalle Valo
2023-12-20 16:42 ` Eric Curtin
2023-12-20 18:14 ` Hector Martin
2023-12-20 19:36 ` Arend van Spriel
2023-12-21 0:49 ` Hector Martin
2023-12-21 9:57 ` Arend van Spriel
2023-12-22 5:10 ` Hector Martin
2023-12-22 12:25 ` Eric Curtin
2024-01-07 9:51 ` Arend van Spriel
2023-12-20 11:32 ` Eric Curtin
2023-12-20 10:16 ` Paul Fertser
2023-12-20 18:02 ` Hector Martin
2023-12-21 14:04 ` Arend van Spriel
2023-12-21 14:11 ` Arend van Spriel
2023-12-22 5:35 ` Hector Martin
2023-12-22 5:28 ` Hector Martin
2023-12-22 7:30 ` Arend Van Spriel
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=ZYLKftqKFJ_PMmF3@archie.me \
--to=bagasdotme@gmail.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=airlied@redhat.com \
--cc=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=dberlin@dberlin.org \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=nick.hollinghurst@raspberrypi.com \
--cc=phil@raspberrypi.com \
--cc=torvalds@linux-foundation.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