From: Kalle Valo <kvalo@codeaurora.org>
To: Ganapathi Bhat <gbhat@marvell.com>
Cc: <linux-wireless@vger.kernel.org>,
Brian Norris <briannorris@chromium.org>,
Cathy Luo <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Xinming Hu <huxm@marvell.com>,
Mangesh Malusare <mmangesh@marvell.com>,
Zhiyuan Yang <yangzy@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>
Subject: Re: [1/2] mwifiex: do not use random MAC for pre-association scanning
Date: Thu, 17 Aug 2017 07:00:10 +0000 (UTC) [thread overview]
Message-ID: <20170817070010.9D5BD6037B@smtp.codeaurora.org> (raw)
In-Reply-To: <1502368886-16539-2-git-send-email-gbhat@marvell.com>
Ganapathi Bhat <gbhat@marvell.com> wrote:
> Driver should use random MAC address only if the scan is
> requested by user(provided NL80211_SCAN_FLAG_RANDOM_ADDR
> is set in scan request). It should not be used for a scan
> performed before association.
>
> Signed-off-by: Ganapathi Bhat <gbhat@marvell.com>
2 patches applied to wireless-drivers-next.git, thanks.
2af2c2c77e5a mwifiex: do not use random MAC for pre-association scanning
89001c1c8dc3 mwifiex: check for NL80211_SCAN_FLAG_RANDOM_ADDR during hidden SSID scan
--
https://patchwork.kernel.org/patch/9893639/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-08-17 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 12:41 [PATCH 0/2] Avoid unnecessary usage of random_mac Ganapathi Bhat
2017-08-10 12:41 ` [PATCH 1/2] mwifiex: do not use random MAC for pre-association scanning Ganapathi Bhat
2017-08-17 7:00 ` Kalle Valo [this message]
2017-08-10 12:41 ` [PATCH 2/2] mwifiex: check for NL80211_SCAN_FLAG_RANDOM_ADDR during hidden SSID scan Ganapathi Bhat
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=20170817070010.9D5BD6037B@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=briannorris@chromium.org \
--cc=cluo@marvell.com \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mmangesh@marvell.com \
--cc=nishants@marvell.com \
--cc=yangzy@marvell.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.