From: Arend van Spriel <arend@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Pontus Fuchs <pontusf@broadcom.com>
Subject: Re: [1/7] brcmfmac: Check if firmware supports p2p
Date: Mon, 15 Jun 2015 20:21:51 +0200 [thread overview]
Message-ID: <557F17BF.9060601@broadcom.com> (raw)
In-Reply-To: <20150615101022.23F92140C1F@smtp.codeaurora.org>
On 06/15/15 12:10, Kalle Valo wrote:
>
>> From: Pontus Fuchs<pontusf@broadcom.com>
>>
>> Add a feature flag to reflect the firmware's p2p capability.
>>
>> Reviewed-by: Pieter-Paul Giesberts<pieterpg@broadcom.com>
>> Reviewed-by: Hante Meuleman<meuleman@broadcom.com>
>> Reviewed-by: Arend Van Spriel<arend@broadcom.com>
>> Signed-off-by: Pontus Fuchs<pontusf@broadcom.com>
>> Signed-off-by: Arend van Spriel<arend@broadcom.com>
>
> Thanks, 7 patches applied to wireless-drivers-next.git:
>
> 2b560d7148eb brcmfmac: Check if firmware supports p2p
> 2e5f66fe9593 brcmfmac: Build wiphy mode and interface combinations dynamically
> 1f0dc59a6de9 brcmfmac: rework .get_station() callback
> 5768f31e4e75 brcmfmac: have sdio return -EIO when device communication is not possible
> f37d69a4babc brcmfmac: free ifp for non-netdev interface in p2p module
> 55479df8840d brcmfmac: move p2p attach/detach functions
> f7a40873d2fa brcmfmac: assure p2pdev is unregistered upon driver unload
Hi Kalle,
As it turns out two patches in this series introduced a new issue (I had
one of those days :-( ). I have fixes for them. Should I send them now
or can it wait until 4.2-rc1 has landed.
Regards,
Arend
> Kalle Valo
next prev parent reply other threads:[~2015-06-15 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 22:12 [PATCH 0/7] brcmfmac: cfg80211 api rework and p2p device fixes Arend van Spriel
2015-06-10 22:12 ` [PATCH 1/7] brcmfmac: Check if firmware supports p2p Arend van Spriel
2015-06-15 10:10 ` [1/7] " Kalle Valo
2015-06-15 18:21 ` Arend van Spriel [this message]
2015-06-15 18:50 ` Kalle Valo
2015-06-10 22:12 ` [PATCH 2/7] brcmfmac: Build wiphy mode and interface combinations dynamically Arend van Spriel
2015-06-10 22:12 ` [PATCH 3/7] brcmfmac: rework .get_station() callback Arend van Spriel
2015-06-10 22:12 ` [PATCH 4/7] brcmfmac: have sdio return -EIO when device communication is not possible Arend van Spriel
2015-06-10 22:12 ` [PATCH 5/7] brcmfmac: free ifp for non-netdev interface in p2p module Arend van Spriel
2015-06-10 22:12 ` [PATCH 6/7] brcmfmac: move p2p attach/detach functions Arend van Spriel
2015-06-10 22:12 ` [PATCH 7/7] brcmfmac: assure p2pdev is unregistered upon driver unload Arend van Spriel
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=557F17BF.9060601@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pontusf@broadcom.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).