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 for 3.10 00/16] brcmfmac: firmware-signalling fixes
Date: Wed, 29 May 2013 21:23:05 +0200	[thread overview]
Message-ID: <51A65599.5040000@broadcom.com> (raw)
In-Reply-To: <20130529184426.GC8770@tuxdriver.com>

On 05/29/2013 08:44 PM, John W. Linville wrote:
> On Wed, May 29, 2013 at 06:38:50PM +0200, Arend van Spriel wrote:
>> This is a somewhat large series and reading the message of the announcement
>> of v3.10-rc3 I think it is good to give our story up front. Firmware-signalling
>> is a new feature merged in for 3.10, which was a major overhaul of the transmit
>> path in brcmfmac. During and after the merge window we still have some blanks
>> in our test coverage and further testing revealed issues with P2P, TDLS, and
>> power-saving clients in AP mode. These issues have been fixed in this series.
>>
>> As said this series is intended for 3.10 and applies to the master branch of
>> the wireless repository.
>>
>> Arend van Spriel (6):
>>    brcmfmac: allow firmware-signal tlv to be longer than specified
>>    brcmfmac: remove fifo bitfield from brcmf_skbuff_cb::if_flags
>>    brcmfmac: rework credit pickup to assure consistent handling
>>    brcmfmac: explicitly indicate sk_buff is sent upon request credit
>>    brcmfmac: reducing debug logging in firmware-signalling code
>>    brcmfmac: Sent TIM information in case of data available.
>>
>> Hante Meuleman (10):
>>    brcmfmac: Take bus flowcontrol at credit mgmt into account.
>>    brcmfmac: On bus flow control use fw signalling or netif.
>>    brcmfmac: For FW signalling it is necessary to track gen bit.
>>    brcmfmac: Correct creditmap when credit borrowing is active.
>>    brcmfmac: Find correct MAC descriptor in case of TDLS.
>>    brcmfmac: fix invalid ifp lookup in firmware-signalling
>>    brcmfmac: Accept only first creditmap event.
>>    brcmfmac: Signalling header push and pull on logic places.
>>    brcmfmac: Fix endless loop when brcmf_fws_commit_skb fails.
>>    brcmfmac: Simplify counting transit count.
>>
>>   drivers/net/wireless/brcm80211/brcmfmac/dhd.h      |    2 +
>>   .../net/wireless/brcm80211/brcmfmac/dhd_linux.c    |   21 +-
>>   drivers/net/wireless/brcm80211/brcmfmac/dhd_sdio.c |    2 +-
>>   drivers/net/wireless/brcm80211/brcmfmac/fwsignal.c |  639 ++++++++++----------
>>   drivers/net/wireless/brcm80211/brcmfmac/fwsignal.h |    1 +
>>   drivers/net/wireless/brcm80211/brcmfmac/usb.c      |    8 +
>>   6 files changed, 340 insertions(+), 333 deletions(-)
>
> Grr...I'll merge it, and pass your plea on to Dave.  But, there can't
> be any more batches like this for 3.10...

Sorry to make you growl. If there are regressions being reported I 
expect that this was it for 3.10 (from us).

Gr. AvS

(not Growling, but Greeting)


      reply	other threads:[~2013-05-29 19:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 16:38 [PATCH for 3.10 00/16] brcmfmac: firmware-signalling fixes Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 01/16] brcmfmac: allow firmware-signal tlv to be longer than specified Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 02/16] brcmfmac: remove fifo bitfield from brcmf_skbuff_cb::if_flags Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 03/16] brcmfmac: Take bus flowcontrol at credit mgmt into account Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 04/16] brcmfmac: rework credit pickup to assure consistent handling Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 05/16] brcmfmac: explicitly indicate sk_buff is sent upon request credit Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 06/16] brcmfmac: reducing debug logging in firmware-signalling code Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 07/16] brcmfmac: On bus flow control use fw signalling or netif Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 08/16] brcmfmac: For FW signalling it is necessary to track gen bit Arend van Spriel
2013-05-29 16:38 ` [PATCH for 3.10 09/16] brcmfmac: Correct creditmap when credit borrowing is active Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 10/16] brcmfmac: Sent TIM information in case of data available Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 11/16] brcmfmac: Find correct MAC descriptor in case of TDLS Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 12/16] brcmfmac: fix invalid ifp lookup in firmware-signalling Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 13/16] brcmfmac: Accept only first creditmap event Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 14/16] brcmfmac: Signalling header push and pull on logic places Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 15/16] brcmfmac: Fix endless loop when brcmf_fws_commit_skb fails Arend van Spriel
2013-05-29 16:39 ` [PATCH for 3.10 16/16] brcmfmac: Simplify counting transit count Arend van Spriel
2013-05-29 16:47 ` [PATCH for 3.10 00/16] brcmfmac: firmware-signalling fixes Arend van Spriel
2013-05-29 18:44 ` John W. Linville
2013-05-29 19:23   ` 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=51A65599.5040000@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).