From: Bob Copeland <me@bobcopeland.com>
To: Masashi Honma <masashi.honma@gmail.com>
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org, j@w1.fi
Subject: Re: [PATCH] cfg80211: Add mesh peer AID setting API
Date: Thu, 30 Jun 2016 07:11:10 -0400 [thread overview]
Message-ID: <20160630111110.GF9984@localhost> (raw)
In-Reply-To: <1467277258-2331-1-git-send-email-masashi.honma@gmail.com>
On Thu, Jun 30, 2016 at 06:00:58PM +0900, Masashi Honma wrote:
> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
> index 7bbb00d..2fa5896 100644
> --- a/include/net/cfg80211.h
> +++ b/include/net/cfg80211.h
> @@ -805,6 +805,7 @@ struct station_parameters {
> u32 sta_modify_mask;
> int listen_interval;
> u16 aid;
> + u16 mesh_aid;
Let's call it peer_aid or mesh_peer_aid or something like that, per my
email on hostapd list. Also you probably saw kbuild robot pointed out
missing documentation for the field.
> diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
> index c503e96..f41fb61 100644
> --- a/net/wireless/nl80211.c
> +++ b/net/wireless/nl80211.c
> @@ -4410,6 +4410,9 @@ static int nl80211_set_station(struct sk_buff *skb, struct genl_info *info)
> nla_get_u8(info->attrs[NL80211_ATTR_STA_PLINK_STATE]);
> if (params.plink_state >= NUM_NL80211_PLINK_STATES)
> return -EINVAL;
> + if (info->attrs[NL80211_ATTR_MESH_PEER_AID])
> + params.mesh_aid = nla_get_u16(
> + info->attrs[NL80211_ATTR_MESH_PEER_AID]);
We need a check against IEEE80211_MAX_AID somewhere.
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2016-06-30 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 9:00 [PATCH] cfg80211: Add mesh peer AID setting API Masashi Honma
2016-06-30 10:03 ` kbuild test robot
2016-06-30 11:11 ` Bob Copeland [this message]
2016-06-30 12:01 ` Masashi Honma
2016-07-01 1:19 ` [PATCH v2] " Masashi Honma
2016-07-06 12:42 ` Johannes Berg
2016-07-06 12:58 ` Bob Copeland
2016-07-06 13:03 ` 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=20160630111110.GF9984@localhost \
--to=me@bobcopeland.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=masashi.honma@gmail.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).