From: Kalle Valo <kvalo@codeaurora.org>
To: Wright Feng <wright.feng@cypress.com>
Cc: arend.vanspriel@broadcom.com, franky.lin@broadcom.com,
hante.meuleman@broadcom.com, linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, wright.feng@cypress.com,
Chi-hsien Lin <Chi-Hsien.Lin@cypress.com>
Subject: Re: brcmfmac: remove setting IBSS mode when stopping AP
Date: Mon, 22 May 2017 15:21:56 +0000 (UTC) [thread overview]
Message-ID: <20170522152156.6446960B75@smtp.codeaurora.org> (raw)
In-Reply-To: <1495099339-7626-1-git-send-email-wright.feng@cypress.com>
Wright Feng <wright.feng@cypress.com> wrote:
> From: Chi-hsien Lin <Chi-Hsien.Lin@cypress.com>
>
> Upon stopping an AP interface the driver disable INFRA mode effectively
> setting the interface in IBSS mode. However, this may affect other
> interfaces running in INFRA mode. For instance, if user creates and stops
> hostap daemon on virtual interface, then association cannot work on
> primary interface because default BSS has been set to IBSS mode in
> firmware side. The IBSS mode should be set when cfg80211 changes the
> interface.
>
> Reviewed-by: Wright Feng <wright.feng@cypress.com>
> Signed-off-by: Chi-hsien Lin <Chi-Hsien.Lin@cypress.com>
> [kvalo@codeaurora.org: rephased commit log based on discussion]
> Signed-off-by: Wright Feng <wright.feng@cypress.com>
Patch applied to wireless-drivers-next.git, thanks.
9029679f66d9 brcmfmac: remove setting IBSS mode when stopping AP
--
https://patchwork.kernel.org/patch/9733205/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-05-22 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 9:22 [PATCH] brcmfmac: remove setting IBSS mode when stopping AP Wright Feng
2017-05-19 4:49 ` Kalle Valo
2017-05-19 7:49 ` Arend van Spriel
2017-05-19 7:54 ` Kalle Valo
2017-05-22 15:21 ` Kalle Valo [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-14 7:11 Philipp Rosenberger
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=20170522152156.6446960B75@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=Chi-Hsien.Lin@cypress.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.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.