From: "Arend van Spriel" <arend@broadcom.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Linux Wireless List" <linux-wireless@vger.kernel.org>,
"Arend van Spriel" <arend@broadcom.com>
Subject: [PATCH 0/9] brcm80211: minor bug fixes for broadcom driver
Date: Wed, 11 Apr 2012 11:52:42 +0200 [thread overview]
Message-ID: <1334137971-3972-1-git-send-email-arend@broadcom.com> (raw)
The series contains a number of patches to resolve some issues found
in our brcmfmac regression testing. The brcmsmac changes are adressing
a problem reported by several people within the community. Last patch
in this series has been marked for stable tree.
This series is based on wireless-next repository and depends on the
following patch message:
Message-ID: <1334098954-7556-2-git-send-email-jim.cromie@gmail.com>
Arend van Spriel (6):
brcm80211: fmac: make brcmf_net_attach() static
brcm80211: fmac: remove primary mac address handling from
brcmf_net_attach
brcm80211: fmac: register primary net device with device mac address
brcm80211: smac: do not use US as fallback regulatory hint
brcm80211: smac: only provide valid regulatory hint
brcm80211: smac: resume transmit fifo upon receiving frames
Franky Lin (3):
brcm80211: fmac: add frame header extension support
brcm80211: fmac: postpone dongle RF enabling.
brcm80211: fmac: clean up chip id table
drivers/net/wireless/brcm80211/brcmfmac/dhd.h | 1 -
drivers/net/wireless/brcm80211/brcmfmac/dhd_cdc.c | 1 +
.../net/wireless/brcm80211/brcmfmac/dhd_common.c | 4 -
.../net/wireless/brcm80211/brcmfmac/dhd_linux.c | 127 +++++++++++---------
drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c | 6 -
drivers/net/wireless/brcm80211/brcmfmac/usb.c | 8 --
drivers/net/wireless/brcm80211/brcmsmac/channel.c | 36 ++++++-
.../net/wireless/brcm80211/brcmsmac/mac80211_if.c | 6 +-
drivers/net/wireless/brcm80211/brcmsmac/main.c | 8 ++
.../net/wireless/brcm80211/include/brcm_hw_ids.h | 40 ++-----
10 files changed, 124 insertions(+), 113 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-04-11 9:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 9:52 Arend van Spriel [this message]
2012-04-11 9:52 ` [PATCH 1/9] brcm80211: fmac: make brcmf_net_attach() static Arend van Spriel
2012-04-11 9:52 ` [PATCH 2/9] brcm80211: fmac: remove primary mac address handling from brcmf_net_attach Arend van Spriel
2012-04-11 9:52 ` [PATCH 3/9] brcm80211: fmac: register primary net device with device mac address Arend van Spriel
2012-04-11 9:52 ` [PATCH 4/9] brcm80211: fmac: add frame header extension support Arend van Spriel
2012-04-11 9:52 ` [PATCH 5/9] brcm80211: fmac: postpone dongle RF enabling Arend van Spriel
2012-04-11 9:52 ` [PATCH 6/9] brcm80211: fmac: clean up chip id table Arend van Spriel
2012-04-11 9:52 ` [PATCH 7/9] brcm80211: smac: do not use US as fallback regulatory hint Arend van Spriel
2012-04-13 14:48 ` Seth Forshee
2012-04-16 8:20 ` Arend van Spriel
2012-04-11 9:52 ` [PATCH 8/9] brcm80211: smac: only provide valid " Arend van Spriel
2012-04-11 9:52 ` [PATCH 9/9] brcm80211: smac: resume transmit fifo upon receiving frames Arend van Spriel
2012-04-13 17:57 ` [PATCH 0/9] brcm80211: minor bug fixes for broadcom driver John W. Linville
2012-04-16 8:51 ` Arend van Spriel
2012-04-16 17:18 ` 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=1334137971-3972-1-git-send-email-arend@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).