From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Sarada Prasanna Garnayak <sarada.prasanna.garnayak@intel.com>
Cc: "johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC PATCH v1] cfg80211/nl80211: add support for AID assignment by driver
Date: Wed, 19 Dec 2018 13:19:56 +0000 [thread overview]
Message-ID: <20181219131949.srxuohfwyn53qxui@bars> (raw)
In-Reply-To: <20181212181249.9039-1-sarada.prasanna.garnayak@intel.com>
Hi,
> Add support for getting and free association ID if the station
> association ID management handled by the WLAN driver/firmware.
>
> Add cfg80211 driver ops and nl80211 API and CMD to request
> the WLAN driver to assign an AID for a station during association
> and release the AID of the station from the WLAN driver/firmware
> station database on disassociation from the AP.
>
> Signed-off-by: Sarada Prasanna Garnayak <sarada.prasanna.garnayak@intel.com>
> ---
> include/net/cfg80211.h | 12 +++++++
> include/uapi/linux/nl80211.h | 11 +++++++
> net/wireless/nl80211.c | 74 ++++++++++++++++++++++++++++++++++++++++++++
> net/wireless/rdev-ops.h | 22 +++++++++++++
> net/wireless/trace.h | 36 +++++++++++++++++++++
> 5 files changed, 155 insertions(+)
Could you please clarify the use-cases for this feature and its potential
users ? Besides, why existing nl80211_set_station can't be used ? It turns
out that there exists station AID field among numerous
'struct station_parameters' fields.
Regards,
Sergey
next prev parent reply other threads:[~2018-12-19 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 18:12 [RFC PATCH v1] cfg80211/nl80211: add support for AID assignment by driver Sarada Prasanna Garnayak
2018-12-19 13:19 ` Sergey Matyukevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-12 18:09 Sarada Prasanna Garnayak
2018-12-13 9:25 ` Kalle Valo
2018-12-13 10:23 ` Johannes Berg
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=20181219131949.srxuohfwyn53qxui@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sarada.prasanna.garnayak@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).