From: Johannes Berg <johannes@sipsolutions.net>
To: Kirill Obukhov <kirill.obukhov@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Add association id to station response
Date: Mon, 22 May 2017 08:17:55 +0200 [thread overview]
Message-ID: <1495433875.2653.4.camel@sipsolutions.net> (raw)
In-Reply-To: <CAP3TkT3VE6FWBXm0K4=-pWLrmsCk4a7wuqc24KdcgYNBRQRyoA@mail.gmail.com> (sfid-20170521_104507_802538_58DA290C)
Hi Kirill,
First of all, please read
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
particularly
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
is important
On Sun, 2017-05-21 at 11:45 +0300, Kirill Obukhov wrote:
> There are unique association id attribute must be passed in station
> add request.
> But we have no way to retrieve ids already in use. To solve issue
> association id attribute added to station response.
This sound fine.
However, it'd be good to mention that you're also adding it to
mac80211, or preferably even split the patch into two, one to add the
feature and one to make use of it in mac80211.
Once you do that, you'll quite likely also notice that with just the
first of the patches, the thing is broken and always reports a 0 AID.
> if (nla_put_u32(msg, NL80211_ATTR_IFINDEX, dev->ifindex) ||
> nla_put(msg, NL80211_ATTR_MAC, ETH_ALEN, mac_addr) ||
> + nla_put_u16(msg, NL80211_ATTR_STA_AID, sinfo->aid) ||
That's because you need to make this conditional on the right filled
flag.
johannes
next prev parent reply other threads:[~2017-05-22 6:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 8:45 [PATCH] nl80211: Add association id to station response Kirill Obukhov
2017-05-22 6:17 ` Johannes Berg [this message]
2017-05-22 9:27 ` Arend van Spriel
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=1495433875.2653.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=kirill.obukhov@gmail.com \
--cc=linux-wireless@vger.kernel.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 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).