From: "Rafał Miłecki" <zajec5@gmail.com>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/12] brcmfmac: scheduled scan cleanup and chip support
Date: Tue, 29 Nov 2016 13:30:06 +0100 [thread overview]
Message-ID: <CACna6rwF+0g3FyiExJr0yf92YDQWbiCm8EGwSNFWR_8G9vC6cg@mail.gmail.com> (raw)
In-Reply-To: <a763eacb-edd9-e551-dad7-456fac580f14@broadcom.com>
On 29 November 2016 at 10:58, Arend Van Spriel
<arend.vanspriel@broadcom.com> wrote:
> On 29-11-2016 8:37, Rafa=C5=82 Mi=C5=82ecki wrote:
>> On 23 November 2016 at 11:25, Arend van Spriel
>> <arend.vanspriel@broadcom.com> wrote:
>>> This patch series contains:
>>> * cleanup of scheduled scan code.
>>> * fix handling schedules scan results for newer chips.
>>> * support for bcm43341 chipset with different chip id.
>>> * support rev6 of PCIe device interface.
>>>
>>> The series is intended for 4.10 and applies to the master branch
>>> of the wireless-drivers-next repository.
>>
>> Tested with BCM43602 on SR400ac router, it still initializes fine, I
>> can create multiple AP interfaces and use them.
>
> Thanks, Rafa=C5=82
>
> Extra testing for the PCIe rev6 support is always appreciated. Although
> I am not sure what rev your 43602 device has. At least we know it is not
> broken ;-)
I guess it's not rev6, my testing was just against possible regressions :)
--=20
Rafa=C5=82
prev parent reply other threads:[~2016-11-29 12:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 10:25 [PATCH 00/12] brcmfmac: scheduled scan cleanup and chip support Arend van Spriel
2016-11-23 10:25 ` [PATCH 01/12] brcmfmac: add pcie host dongle interface rev6 support Arend van Spriel
2016-11-29 15:30 ` [01/12] " Kalle Valo
2016-11-23 10:25 ` [PATCH 02/12] brcmfmac: add support for 43341 chip Arend van Spriel
2016-11-23 10:25 ` [PATCH 03/12] brcmfmac: move pno helper functions in separate source file Arend van Spriel
2016-11-29 7:08 ` Rafał Miłecki
2016-11-29 7:57 ` Johannes Berg
2016-11-29 9:23 ` Arend Van Spriel
2016-11-29 12:29 ` Rafał Miłecki
2016-11-29 14:54 ` Kalle Valo
2016-11-23 10:25 ` [PATCH 04/12] brcmfmac: fix handling ssids in .sched_scan_start() callback Arend van Spriel
2016-11-23 10:25 ` [PATCH 05/12] brcmfmac: change prototype for brcmf_do_escan() Arend van Spriel
2016-11-23 10:25 ` [PATCH 06/12] brcmfmac: make internal escan more generic Arend van Spriel
2016-11-23 10:25 ` [PATCH 07/12] brcmfmac: split up brcmf_pno_config() function Arend van Spriel
2016-11-23 10:25 ` [PATCH 08/12] brcmfmac: move scheduled scan activation to pno source file Arend van Spriel
2016-11-23 10:25 ` [PATCH 09/12] brcmfmac: use provided channels for scheduled scan Arend van Spriel
2016-11-23 10:25 ` [PATCH 10/12] brcmfmac: remove restriction from .sched_scan_start() callback Arend van Spriel
2016-11-23 10:25 ` [PATCH 11/12] brcmfmac: use requested scan interval in scheduled scan Arend van Spriel
2016-11-23 10:25 ` [PATCH 12/12] brcmfmac: fix scheduled scan result handling for newer chips Arend van Spriel
2016-11-29 7:37 ` [PATCH 00/12] brcmfmac: scheduled scan cleanup and chip support Rafał Miłecki
2016-11-29 9:58 ` Arend Van Spriel
2016-11-29 12:30 ` Rafał Miłecki [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=CACna6rwF+0g3FyiExJr0yf92YDQWbiCm8EGwSNFWR_8G9vC6cg@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=arend.vanspriel@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 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).