From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>,
linux-wireless@vger.kernel.org
Cc: Tamizh Chelvam <tamizhr@codeaurora.org>
Subject: Re: [RFC PATCH 0/4] cfg80211: updates and fixes for TID specific configuration
Date: Fri, 24 Apr 2020 12:18:35 +0200 [thread overview]
Message-ID: <db1081861ba7e7ee334c3e50494ff3cd34d9963d.camel@sipsolutions.net> (raw)
In-Reply-To: <20200420113437.16998-1-sergey.matyukevich.os@quantenna.com>
Hi,
> This patch series contains several minor fixes and enhancements for TID
> specific configuration functionality. The first three patches include
> minor fixes and TID specific AMSDU configuration.
Looks good, though I just saw you noticed a small bug :)
> The last patch is somewhat controversial, so the series is marked as RFC.
> The last patch simplifies current override logic. It suggests to make no
> difference between 'specific peer' and 'all peers' cases and to apply
> new TID configuration immediately after resetting the previous one.
Yeah, I tend to agree.
Can you resend with the small fix?
johannes
next prev parent reply other threads:[~2020-04-24 10:18 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
2020-04-20 11:34 ` [RFC PATCH 4/4] nl80211: simplify peer specific TID configuration Sergey Matyukevich
2020-04-24 10:18 ` Johannes Berg [this message]
2020-04-24 10:26 ` [RFC PATCH 0/4] cfg80211: updates and fixes for TID specific configuration 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=db1081861ba7e7ee334c3e50494ff3cd34d9963d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=sergey.matyukevich.os@quantenna.com \
--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;
as well as URLs for NNTP newsgroup(s).