From: Kalle Valo <kvalo@codeaurora.org>
To: Yen-lin Lai <yenlinlai@chromium.org>
Cc: linux-wireless@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Yen-lin Lai <yenlinlai@chromium.org>,
Amitkumar Karwar <amitkarwar@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ganapathi Bhat <ganapathi.bhat@nxp.com>,
Jakub Kicinski <kuba@kernel.org>,
Xinming Hu <huxinming820@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] mwifiex: Report connected BSS with cfg80211_connect_bss()
Date: Mon, 8 Feb 2021 11:17:44 +0000 (UTC) [thread overview]
Message-ID: <20210208111744.0C28AC433C6@smtp.codeaurora.org> (raw)
In-Reply-To: <20210201070649.1667209-1-yenlinlai@chromium.org>
Yen-lin Lai <yenlinlai@chromium.org> wrote:
> When a network is moved or reconfigured on the different channel, there
> can be multiple BSSes with the same BSSID and SSID in scan result
> before the old one expires. Then, it can cause cfg80211_connect_result
> to map current_bss to a bss with the wrong channel.
>
> Let mwifiex_cfg80211_assoc return the selected BSS and then the caller
> can report it cfg80211_connect_bss.
>
> Signed-off-by: Yen-lin Lai <yenlinlai@chromium.org>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
Patch applied to wireless-drivers-next.git, thanks.
b7fd26c913f1 mwifiex: Report connected BSS with cfg80211_connect_bss()
--
https://patchwork.kernel.org/project/linux-wireless/patch/20210201070649.1667209-1-yenlinlai@chromium.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-02-08 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 7:06 [PATCH] mwifiex: Report connected BSS with cfg80211_connect_bss() Yen-lin Lai
2021-02-01 22:03 ` Brian Norris
2021-02-08 11:17 ` Kalle Valo [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=20210208111744.0C28AC433C6@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=amitkarwar@gmail.com \
--cc=briannorris@chromium.org \
--cc=davem@davemloft.net \
--cc=ganapathi.bhat@nxp.com \
--cc=huxinming820@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yenlinlai@chromium.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 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.