On 2018-11-09 17:54, Johannes Berg wrote:
On Fri, 2018-11-09 at 09:40 +0000, Sergey Matyukevich wrote:
Ok. So if driver receives retry value (-1), it should reset to some
default value known to driver or firmware. IMHO it worth making it
more explicit: in its current form this convention will not be obvious
for driver authors. Though I don't have a good idea how to do it.
Maybe merge both aggregation and retry cfg80211 callbacks into one
and use structure for params and bitmask for operations...
I think we want that anyway, I just suggested to also add the "noack"
to
the same API, and indeed it's pointless to set retries and noack.
Sure, I'll change it to a single api for all the tid_config operations.
