From: "Arend van Spriel" <arend@broadcom.com>
To: "Arend van Spriel" <arend@broadcom.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/17] fix mac80211 callback in brcmsmac and brcmfmac refactor
Date: Fri, 21 Oct 2011 16:07:23 +0200 [thread overview]
Message-ID: <4EA17C9B.3070106@broadcom.com> (raw)
In-Reply-To: <1319205319-16891-1-git-send-email-arend@broadcom.com>
On 10/21/2011 03:55 PM, Arend van Spriel wrote:
> Johannes Berg commented on our use of the start/stop callbacks in brcmsmac
> and we changed those callbacks. In rfkill testing it revealed a problem which
> has been fixed in this series as well.
>
> The brcmfmac driver had some restructuring in preparation of USB support
> for new devices.
>
> This patch series applies to the wireless-testing repository and depends on the
> series posted on Oct 18, 2011 with message id:
>
> Message-ID: <1318939391-19495-1-git-send-email-arend@broadcom.com>
>
John,
I sent this series too quickly. Can you please drop this whole series. I
will resubmit a v2. Sorry for the disturbance.
Gr. AvS
prev parent reply other threads:[~2011-10-21 14:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 13:55 [PATCH 00/17] fix mac80211 callback in brcmsmac and brcmfmac refactor Arend van Spriel
2011-10-21 13:55 ` [PATCH 01/17] brcm80211: fmac: allow wd timer to be disabled when bus down Arend van Spriel
2011-10-21 13:55 ` [PATCH 02/17] brcm80211: fmac: use brcmf_del_if for all net devices Arend van Spriel
2011-10-21 13:55 ` [PATCH 03/17] brcm80211: smac: removed MPC related code Arend van Spriel
2011-10-21 13:55 ` [PATCH 04/17] brcm80211: smac: removed MPC related variables Arend van Spriel
2011-10-21 13:55 ` [PATCH 05/17] brcm80211: smac: removed down-on-watchdog MPC functionality Arend van Spriel
2011-10-21 13:55 ` [PATCH 06/17] brcm80211: smac: removed down-on-rf-kill functionality Arend van Spriel
2011-10-21 13:55 ` [PATCH 07/17] brcm80211: smac: bugfix for tx mute in brcms_b_init() Arend van Spriel
2011-10-21 13:55 ` [PATCH 08/17] brcm80211: smac: fixed inconsistency in transmit mute Arend van Spriel
2011-10-21 13:55 ` [PATCH 09/17] brcm80211: smac: modified Mac80211 callback interface Arend van Spriel
2011-10-21 13:55 ` [PATCH 10/17] brcm80211: smac: mute transmit on ops_start Arend van Spriel
2011-10-21 13:55 ` [PATCH 11/17] brcm80211: smac: changed check to confirm STA only support Arend van Spriel
2011-10-21 13:55 ` [PATCH 12/17] brcm80211: smac: rename buffer endianess conversion functions Arend van Spriel
2011-10-21 13:55 ` [PATCH 13/17] brcm80211: smac: use sk_buff list for handling frames in receive path Arend van Spriel
2011-10-21 13:55 ` [PATCH 14/17] brcm80211: fmac: use brcmf_add_if for all net devices Arend van Spriel
2011-10-21 13:55 ` [PATCH 15/17] brcm80211: fmac: store brcmf_if in net device private data Arend van Spriel
2011-10-21 13:55 ` [PATCH 16/17] brcm80211: fmac: remove state from brcmf_if in fullmac Arend van Spriel
2011-10-21 13:55 ` [PATCH 17/17] brcm80211: smac: change buffer endianess convert function interface Arend van Spriel
2011-10-21 14: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=4EA17C9B.3070106@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).