From: Kalle Valo <kvalo@codeaurora.org>
To: Arend van Spriel <arend@broadcom.com>
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 21:50:39 +0300 [thread overview]
Message-ID: <874mm8ajr4.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <557F17BF.9060601@broadcom.com> (Arend van Spriel's message of "Mon, 15 Jun 2015 20:21:51 +0200")
Arend van Spriel <arend@broadcom.com> writes:
>> 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
>
> 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.
Please send them now and I'll try to apply them as soon as possible.
--
Kalle Valo
next prev parent reply other threads:[~2015-06-15 18:50 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
2015-06-15 18:50 ` Kalle Valo [this message]
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=874mm8ajr4.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.