From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 00/10] brcmfmac: device support and fixes
Date: Sat, 9 May 2015 18:29:50 +0200 [thread overview]
Message-ID: <554E35FE.4060805@broadcom.com> (raw)
In-Reply-To: <87oaltltlh.fsf@kamboji.qca.qualcomm.com>
On 05/09/15 16:21, Kalle Valo wrote:
> Hi Arend,
>
> Arend van Spriel<arend@broadcom.com> writes:
>
>> This series include some fixes related to SDIO suspend and resume,
>> wiphy band info and changes in regulatory settings. Furthermore,
>> support for BCM4324 SDIO and BCM4358 PCIe is added. Finally,
>> some patches from Hante that should enable support of PCIe devices
>> on router platforms.
>
> Your patch series are always top notch but I still would like to ask for
> one small formatting change :) It would make my life easier if you could
> list the major changes like this:
>
> * SDIO suspend and resume fixes
> * wiphy band info and changes in regulatory settings
> * add support for BCM4324 SDIO and BCM4358 PCIe
> * enable support of PCIe devices on router platforms (Hante)
>
> That way I could directly copy your list to the pull request I send to
> Dave.
No problem. We want our lives to be as easy as possible ;-)
Regards,
Arend
prev parent reply other threads:[~2015-05-09 16:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 18:10 [PATCH 00/10] brcmfmac: device support and fixes Arend van Spriel
2015-04-14 18:10 ` [PATCH 01/10] brcmfmac: use static superset of channels for wiphy bands Arend van Spriel
2015-05-09 13:27 ` [01/10] " Kalle Valo
2015-04-14 18:10 ` [PATCH 02/10] brcmfmac: update wiphy band information upon updating regulatory domain Arend van Spriel
2015-04-14 18:10 ` [PATCH 03/10] brcmfmac: add description for feature flags Arend van Spriel
2015-04-14 18:10 ` [PATCH 04/10] brcmfmac: make scheduled scan support conditional Arend van Spriel
2015-04-14 18:10 ` [PATCH 05/10] brcmfmac: add support for BCM4324 rev B5 chipset Arend van Spriel
2015-04-14 18:10 ` [PATCH 06/10] brcmfmac: process interrupt regardless sdiod state Arend van Spriel
2015-04-14 18:10 ` [PATCH 07/10] brcmfmac: fix sdio suspend and resume Arend van Spriel
2015-04-22 7:32 ` Ulf Hansson
2015-04-28 16:14 ` Kalle Valo
2015-04-28 16:50 ` Arend van Spriel
2015-05-04 11:16 ` Ulf Hansson
2015-04-14 18:10 ` [PATCH 08/10] brcmfmac: add support for BCM4358 PCIe device Arend van Spriel
2015-04-14 18:10 ` [PATCH 09/10] brcmfmac: add additional 43602 pcie device id Arend van Spriel
2015-04-14 18:10 ` [PATCH 10/10] brcmfmac: Add support for multiple PCIE devices in nvram Arend van Spriel
2015-04-15 14:52 ` Rafał Miłecki
[not found] ` <F51492713EF10846800D8C0ED37A7DCE019304D6@SJEXCHMB15.corp.ad.broadcom.com>
2015-04-17 7:45 ` Rafał Miłecki
2015-04-17 8:50 ` Arend van Spriel
2015-04-20 11:26 ` Rafał Miłecki
2015-04-20 17:12 ` Arend van Spriel
2015-04-20 18:49 ` Rafał Miłecki
2015-04-20 20:16 ` Arend van Spriel
2015-04-21 10:16 ` Rafał Miłecki
2015-04-21 10:24 ` Arend van Spriel
2015-04-17 7:55 ` Rafał Miłecki
2015-04-24 8:58 ` Rafał Miłecki
2015-05-09 14:21 ` [PATCH 00/10] brcmfmac: device support and fixes Kalle Valo
2015-05-09 16:29 ` 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=554E35FE.4060805@broadcom.com \
--to=arend@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).