linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/7] brcmfmac: cleanup and new device support
Date: Thu, 3 Oct 2013 13:25:47 +0200	[thread overview]
Message-ID: <524D543B.7010906@broadcom.com> (raw)
In-Reply-To: <1380107146-24026-1-git-send-email-arend@broadcom.com>

On 09/25/2013 01:05 PM, Arend van Spriel wrote:
> This series has a few cleanup patches fixing a sparse error, cleaning
> up the rx path and also changing the firmware filename approach after
> getting feedback on this by Stephen Warren. The remaining patches are
> adding support for the BCM4339 SDIO chipset.
>
> This series is intended for v3.13 kernel and applies to the master
> branch of the wireless-next repository.

Hi John,

Did you miss this series from last week?

Regards,
Arend

> Arend van Spriel (2):
>    brcmfmac: fix sparse error 'bad constant expression'
>    brcmfmac: rework rx path bus interface
>
> Franky Lin (4):
>    brcmfmac: sync firmware event list
>    brcmfmac: add BCM4339 SDIO interface support
>    brcmfmac: add valid core index check in related functions
>    brcmfmac: reserve memory for bus layer in sk_buff::cb
>
> Hante Meuleman (1):
>    brcmfmac: Use fw filename and nvram based of devid for sdio.
>
>   .../net/wireless/brcm80211/brcmfmac/bcmsdh_sdmmc.c |   11 +-
>   drivers/net/wireless/brcm80211/brcmfmac/dhd.h      |    2 -
>   drivers/net/wireless/brcm80211/brcmfmac/dhd_bus.h  |    2 +-
>   .../net/wireless/brcm80211/brcmfmac/dhd_linux.c    |   38 ++--
>   drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c |  234 ++++++++++++--------
>   drivers/net/wireless/brcm80211/brcmfmac/fweh.h     |    5 +-
>   drivers/net/wireless/brcm80211/brcmfmac/fwsignal.c |    2 +
>   .../net/wireless/brcm80211/brcmfmac/sdio_chip.c    |   28 +++
>   .../net/wireless/brcm80211/brcmfmac/sdio_chip.h    |    8 +
>   drivers/net/wireless/brcm80211/brcmfmac/usb.c      |    5 +-
>   .../net/wireless/brcm80211/include/brcm_hw_ids.h   |    1 +
>   11 files changed, 211 insertions(+), 125 deletions(-)
>



  parent reply	other threads:[~2013-10-03 11:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 11:05 [PATCH 0/7] brcmfmac: cleanup and new device support Arend van Spriel
2013-09-25 11:05 ` [PATCH 1/7] brcmfmac: sync firmware event list Arend van Spriel
2013-09-25 11:05 ` [PATCH 2/7] brcmfmac: add BCM4339 SDIO interface support Arend van Spriel
2013-09-25 11:05 ` [PATCH 3/7] brcmfmac: add valid core index check in related functions Arend van Spriel
2013-09-25 11:05 ` [PATCH 4/7] brcmfmac: reserve memory for bus layer in sk_buff::cb Arend van Spriel
2013-09-25 11:05 ` [PATCH 5/7] brcmfmac: fix sparse error 'bad constant expression' Arend van Spriel
2013-09-25 11:05 ` [PATCH 6/7] brcmfmac: Use fw filename and nvram based of devid for sdio Arend van Spriel
2013-09-25 11:05 ` [PATCH 7/7] brcmfmac: rework rx path bus interface Arend van Spriel
2013-10-03 11:25 ` Arend van Spriel [this message]
2013-10-03 20:21   ` [PATCH 0/7] brcmfmac: cleanup and new device support John W. Linville

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=524D543B.7010906@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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;
as well as URLs for NNTP newsgroup(s).