From: Mathy Vanhoef <vanhoefm@gmail.com>
To: radiotap@netbsd.org
Subject: Re: [RFA] TX Flags field
Date: Sat, 17 Oct 2020 00:06:49 +0400 [thread overview]
Message-ID: <CAFXAJYydMGh+vT9-dVTRi82=pyp0xx4xSmTN023A6rOnW55bHA@mail.gmail.com> (raw)
In-Reply-To: <CAFXAJYyXk+T1SZOjV0wBwfqsk4txMYEXajXmhvugW2ppcWVqtQ@mail.gmail.com>
I think this can be adopted now?
In the meantime OpenBSD has also removed the "hardware_queue" that was
conflicting with the bit number for the TX flags field, see
https://marc.info/?l=openbsd-cvs&m=160223361331358&w=2 This means the
following remark that the TX flags field clashes with OpenBSD does not
have to be included anymore:
On Fri, Oct 9, 2020 at 2:28 PM Mathy Vanhoef <vanhoefm@gmail.com> wrote:
> Used by NetBSD and Linux, clashes with ../hardware queue\_ as used in OpenBSD.
Best regards,
Mathy
next prev parent reply other threads:[~2020-10-16 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 10:28 [RFA] TX Flags field Mathy Vanhoef
2020-10-16 20:06 ` Mathy Vanhoef [this message]
2020-10-16 20:20 ` Johannes Berg
2020-10-27 7:37 ` 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='CAFXAJYydMGh+vT9-dVTRi82=pyp0xx4xSmTN023A6rOnW55bHA@mail.gmail.com' \
--to=vanhoefm@gmail.com \
--cc=radiotap@netbsd.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).