Re: Proposed Tx flag: don't reorder frames
Johannes Berg <[email protected]> Thu, 17 Sep 2020 11:57:30 +0200
| Newsgroups | org.netbsd.radiotap |
|---|---|
| Message-ID | <[email protected]> |
On Sun, 2020-08-30 at 04:05 +0400, Mathy Vanhoef wrote: > To follow up on this: the only downside is that OpenBSD is using the > TX flags identifier to report the hardware queue on which a frame was > received. > > Since Linux and NetBSD are using TX flags, and Wireshark decided to > already accept the patch to support TX flags as well, it seems to make > sense to let this identifier represent TX flags. Then only one > implementation (OpenBSD) would have to be updated to match this. I'm > assuming nobody would be against this, since there have been more than > three weeks to discuss this, and nobody brought this up. > > What's the next step? Adopt the proposal in one week if there are no > further objections? Sorry this took so long. I think we need to make a proper proposal again for the whole TX flags field, since that was never officially adopted? > PS: Is the archive on https://lore.kernel.org/radiotap/ being updated? Looks like no, I have asked the admins there, but didn't hear back yet. johannes