All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/10] brcmfmac: new device support and more
Date: Tue, 6 Jan 2015 20:07:33 +0100	[thread overview]
Message-ID: <54AC3275.7040802@broadcom.com> (raw)
In-Reply-To: <87fvbnycvr.fsf@kamboji.qca.qualcomm.com>

On 01/06/15 19:36, Kalle Valo wrote:
> Arend van Spriel<arend@broadcom.com>  writes:
>
>> Here a first batch for v3.20. This series adds support for the
>> BCM43340 and BCM43341 SDIO chipsets. A number of changes are
>> related to AP mode and some fixes of potential issues that do
>> not seem to qualify for the wireless tree.
>>
>> This series is intended for v3.20 and applies to the master
>> branch of the *new* wireless-next repository.
>>
>> Arend van Spriel (5):
>>    brcmfmac: Add support for bcm43340/1 wireless chipsets
>>    brcmfmac: get rid of duplicate SDIO device identifiers
>>    brcmfmac: remove unused/duplicate defines in chip.c
>>    brcmfmac: follow user-space regulatory domain selection
>>    brcmfmac: enable 802.11d support in firmware
>>
>> Hante Meuleman (5):
>>    brcmfmac: Fix incorrect casting of 64 bit physical address.
>>    brcmfmac: Fix possible dereference of NULL pointer.
>>    brcmfmac: Fix WEP configuration for AP mode.
>>    brcmfmac: Change error log in standard log for rxbufpost.
>>    brcmfmac: signal completion of 802.1x.
>
> I applied these patches:
>
> 98027769828f brcmfmac: enable 802.11d support in firmware
> 6b89dcb35bfc brcmfmac: signal completion of 802.1x.
> 63db1a499cee brcmfmac: follow user-space regulatory domain selection
> d2e2472cd197 brcmfmac: Change error log in standard log for rxbufpost.
> 118eb304d055 brcmfmac: Fix WEP configuration for AP mode.
> f714e58e19a5 brcmfmac: remove unused/duplicate defines in chip.c
> 83297aaa8fde brcmfmac: Fix incorrect casting of 64 bit physical address.
>
> I dropped two due based on discussion and one patch didn't apply.
>
Thanks, Kalle

I will resend that last one mentioned. Probably depends on (one of) the 
two dropped patches.

Regards,
Arend


      reply	other threads:[~2015-01-06 19:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 11:43 [PATCH 00/10] brcmfmac: new device support and more Arend van Spriel
2014-12-21 11:43 ` [PATCH 01/10] brcmfmac: Fix incorrect casting of 64 bit physical address Arend van Spriel
2014-12-21 17:24   ` Joe Perches
2014-12-21 11:43 ` [PATCH 02/10] brcmfmac: Fix possible dereference of NULL pointer Arend van Spriel
2014-12-23 17:07   ` Arend van Spriel
2014-12-21 11:43 ` [PATCH 03/10] brcmfmac: Add support for bcm43340/1 wireless chipsets Arend van Spriel
2014-12-21 17:50   ` Marcel Holtmann
2014-12-21 19:56     ` Arend van Spriel
2014-12-21 20:14       ` Rafał Miłecki
2014-12-22  9:05         ` Arend van Spriel
2014-12-22  9:33           ` Rafał Miłecki
2014-12-21 11:43 ` [PATCH 04/10] brcmfmac: get rid of duplicate SDIO device identifiers Arend van Spriel
2015-01-06 18:35   ` Kalle Valo
2014-12-21 11:43 ` [PATCH 05/10] brcmfmac: remove unused/duplicate defines in chip.c Arend van Spriel
2014-12-21 11:43 ` [PATCH 06/10] brcmfmac: Fix WEP configuration for AP mode Arend van Spriel
2014-12-21 11:43 ` [PATCH 07/10] brcmfmac: Change error log in standard log for rxbufpost Arend van Spriel
2014-12-21 11:43 ` [PATCH 08/10] brcmfmac: follow user-space regulatory domain selection Arend van Spriel
2014-12-21 11:43 ` [PATCH 09/10] brcmfmac: signal completion of 802.1x Arend van Spriel
2014-12-21 11:43 ` [PATCH 10/10] brcmfmac: enable 802.11d support in firmware Arend van Spriel
2015-01-06 18:36 ` [PATCH 00/10] brcmfmac: new device support and more Kalle Valo
2015-01-06 19:07   ` Arend van Spriel [this message]

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=54AC3275.7040802@broadcom.com \
    --to=arend@broadcom.com \
    --cc=kvalo@codeaurora.org \
    --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.