From: Sven Eckelmann <sven@open-mesh.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iw: add VHT80 support for 802.11s
Date: Wed, 25 Nov 2015 09:27:20 +0100 [thread overview]
Message-ID: <1665268.sMoWlW2lMO@bentobox> (raw)
In-Reply-To: <CAGRGNgUzFuK=r4HTtC0VkBc-5rLEHA99GB3VuyA6T7Ch6nr2kw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
On Wednesday 25 November 2015 08:42:44 Julian Calaby wrote:
> > -COMMAND(mesh, join, "<mesh ID> [[freq <freq in MHz> <HT20|HT40+|HT40-|NOHT>]"
> > +COMMAND(mesh, join, "<mesh ID> [[freq <freq in MHz> <HT20|HT40+|HT40-|NOHT|80MHz>]"
>
> Should NOHT remain last in the list?
This would be inconsistent. ibss join also has 80MHz as the last entry
in the usage text and NOHT is the entry after "HT20|HT40+|HT40-".
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-25 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 17:42 iw: add VHT80 support for 802.11s Sven Eckelmann
2015-11-24 21:42 ` Julian Calaby
2015-11-25 8:27 ` Sven Eckelmann [this message]
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=1665268.sMoWlW2lMO@bentobox \
--to=sven@open-mesh.com \
--cc=johannes@sipsolutions.net \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.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