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 V2 0/7] brcmfmac: support devices from multiple vendors
Date: Thu, 01 Dec 2022 13:12:29 +0200	[thread overview]
Message-ID: <87fsdz4btu.fsf@kernel.org> (raw)
In-Reply-To: <9dfeb220-b81b-83de-db91-9bb57014309f@broadcom.com> (Arend van Spriel's message of "Tue, 29 Nov 2022 14:58:12 +0100")

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

> On 11/29/2022 2:54 PM, Arend van Spriel wrote:
>> Took my sweet time coming with this follow-up series, but here
>> it is. Hopefully, sending patches is working for me now.
>>
>> The bcm43xx family of wifi chipsets found its way to different
>> groups inside and outside Broadcom. For the fullmac devices this
>> means that in those difference groups firmware is being developed
>> and the firmware api is bound to diverge. This series introduces
>> a design change to accomodate supporting multiple firmware api's.
>> The vender-specific support can be compiled in brcmfmac or
>> built as a separate module. Currently the vendor-specific support
>> does not have any real effect. At the momemt looking into SAE support
>> which appear to be different for Cypress devices so that might be a
>> first use-case.
>>
>> The patches apply to the main branch of the wireless-next repository.
>
> Just realized I forgot the 'wifi:' prefix. Hopefully you can forgive
> me this time? If not, I can resend.

Yeah, I can add that. When we switched to using "wifi:" I was mentally
(and in my tools) prepared to adding those the next couple of years :)

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

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

  reply	other threads:[~2022-12-01 11:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 13:54 [PATCH V2 0/7] brcmfmac: support devices from multiple vendors Arend van Spriel
2022-11-29 13:54 ` [PATCH V2 1/7] brcmfmac: add function to unbind device to bus layer api Arend van Spriel
2022-12-08 14:44   ` [V2,1/7] wifi: " Kalle Valo
2022-11-29 13:54 ` [PATCH V2 2/7] brcmfmac: add firmware vendor info in driver info Arend van Spriel
2022-11-29 13:54 ` [PATCH V2 3/7] brcmfmac: add support for vendor-specific firmware api Arend van Spriel
2022-11-29 13:54 ` [PATCH V2 4/7] brcmfmac: add support for Cypress " Arend van Spriel
2022-11-29 13:54 ` [PATCH V2 5/7] brcmfmac: add support Broadcom BCA " Arend van Spriel
2022-11-29 13:54 ` [PATCH V2 6/7] brcmfmac: add vendor name in revinfo debugfs file Arend van Spriel
2022-11-29 13:54 ` [PATCH V2 7/7] brcmfmac: introduce BRCMFMAC exported symbols namespace Arend van Spriel
2022-11-29 13:58 ` [PATCH V2 0/7] brcmfmac: support devices from multiple vendors Arend van Spriel
2022-12-01 11:12   ` Kalle Valo [this message]
2022-12-01 11:21     ` 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=87fsdz4btu.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.