From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: linux-wireless@vger.kernel.org
Cc: Tamizh Chelvam <tamizhr@codeaurora.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFC PATCH 3/4] cfg80211: add support for TID specific AMSDU configuration
Date: Fri, 24 Apr 2020 13:04:02 +0300 [thread overview]
Message-ID: <20200424100402.ty3i5lfqldhrivva@bars> (raw)
In-Reply-To: <20200420113437.16998-4-sergey.matyukevich.os@quantenna.com>
> This patch adds support to control per TID MSDU aggregation
> using the NL80211_TID_CONFIG_ATTR_AMSDU_CTRL attribute.
>
> Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
> ---
> include/net/cfg80211.h | 4 +++-
> include/uapi/linux/nl80211.h | 10 +++++++---
> net/wireless/nl80211.c | 6 ++++++
> 3 files changed, 16 insertions(+), 4 deletions(-)
This patch misses adding new policy for AMSDU NL80211 attribute.
To be fixed in v2.
Regards,
Sergey
next prev parent reply other threads:[~2020-04-24 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:34 [RFC PATCH 0/4] cfg80211: updates and fixes for TID specific configuration Sergey Matyukevich
2020-04-20 11:34 ` [RFC PATCH 1/4] cfg80211: fix mask type in cfg80211_tid_cfg structure Sergey Matyukevich
2020-04-20 11:34 ` [RFC PATCH 2/4] mac80211: fix variable names in TID config methods Sergey Matyukevich
2020-04-20 11:34 ` [RFC PATCH 3/4] cfg80211: add support for TID specific AMSDU configuration Sergey Matyukevich
2020-04-24 10:04 ` Sergey Matyukevich [this message]
2020-04-20 11:34 ` [RFC PATCH 4/4] nl80211: simplify peer specific TID configuration Sergey Matyukevich
2020-04-24 10:18 ` [RFC PATCH 0/4] cfg80211: updates and fixes for TID specific configuration Johannes Berg
2020-04-24 10:26 ` Sergey Matyukevich
2020-04-24 10:29 ` 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=20200424100402.ty3i5lfqldhrivva@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tamizhr@codeaurora.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