From: Kalle Valo <kvalo@codeaurora.org>
To: Wright Feng <wright.feng@cypress.com>
Cc: linux-wireless@vger.kernel.org, chi-hsien.lin@cypress.com,
wright.feng@cypress.com, brcm80211-dev-list@broadcom.com,
brcm80211-dev-list@cypress.com,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>
Subject: Re: [PATCH 1/3] brcmfmac: support the second p2p connection
Date: Wed, 6 May 2020 08:40:06 +0000 (UTC) [thread overview]
Message-ID: <20200506084006.AE6D2C43637@smtp.codeaurora.org> (raw)
In-Reply-To: <1588572453-194663-2-git-send-email-wright.feng@cypress.com>
Wright Feng <wright.feng@cypress.com> wrote:
> With RSDB feature, firmware is able to support two P2P-AGO or two
> P2P-GC at the same time. So we add the second p2p connection type
> to map to the second P2P connection bsscfg.
>
> Signed-off-by: Wright Feng <wright.feng@cypress.com>
> Signed-off-by: Chi-hsien Lin <chi-hsien.lin@cypress.com>
3 patches applied to wireless-drivers-next.git, thanks.
babfd3caf356 brcmfmac: support the second p2p connection
9c29da3f4e7e brcmfmac: Fix P2P Group Formation failure via Go-neg method
7f26cedfc9fd brcmfmac: Add P2P Action Frame retry delay to fix GAS Comeback Response failure issue
--
https://patchwork.kernel.org/patch/11525053/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-05-06 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 6:07 [PATCH 0/3] brcmfmac: p2p fixes and the second connection support Wright Feng
2020-05-04 6:07 ` [PATCH 1/3] brcmfmac: support the second p2p connection Wright Feng
2020-05-06 8:40 ` Kalle Valo [this message]
2020-05-04 6:07 ` [PATCH 2/3] brcmfmac: Fix P2P Group Formation failure via Go-neg method Wright Feng
2020-05-04 6:07 ` [PATCH 3/3] brcmfmac: Add P2P Action Frame retry delay to fix GAS Comeback Response failure issue Wright Feng
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=20200506084006.AE6D2C43637@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brcm80211-dev-list@cypress.com \
--cc=chi-hsien.lin@cypress.com \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wright.feng@cypress.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.