From: Johannes Berg <johannes@sipsolutions.net>
To: Peter Oh <poh@qca.qualcomm.com>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] cfg80211: add VHT support for Mesh
Date: Thu, 12 Nov 2015 21:03:25 +0100 [thread overview]
Message-ID: <1447358605.2131.3.camel@sipsolutions.net> (raw)
In-Reply-To: <ab294ba62856f00c06dde10b1bf57f5f341a7198.1447351137.git.poh@qca.qualcomm.com>
On Thu, 2015-11-12 at 09:59 -0800, Peter Oh wrote:
> Add NL80211_EXT_FEATURE_VHT_MESH flag to allow drivers
> to indicate support for VHT in Mesh mode.
> This flag will be used by wireless drivers to indicate
> the capability of VHT Mesh support and wpa_supplicant to inspect
> wireless drivers' capability of VHT Mesh.
> In addition to this patch, separate patches to ath10k driver and
> wpa_supplicant are also sent out.
>
Sorry, still doesn't make sense. What does userspace even need to know
this *for*?
johannes
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Peter Oh <poh@qca.qualcomm.com>, ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] cfg80211: add VHT support for Mesh
Date: Thu, 12 Nov 2015 21:03:25 +0100 [thread overview]
Message-ID: <1447358605.2131.3.camel@sipsolutions.net> (raw)
In-Reply-To: <ab294ba62856f00c06dde10b1bf57f5f341a7198.1447351137.git.poh@qca.qualcomm.com>
On Thu, 2015-11-12 at 09:59 -0800, Peter Oh wrote:
> Add NL80211_EXT_FEATURE_VHT_MESH flag to allow drivers
> to indicate support for VHT in Mesh mode.
> This flag will be used by wireless drivers to indicate
> the capability of VHT Mesh support and wpa_supplicant to inspect
> wireless drivers' capability of VHT Mesh.
> In addition to this patch, separate patches to ath10k driver and
> wpa_supplicant are also sent out.
>
Sorry, still doesn't make sense. What does userspace even need to know
this *for*?
johannes
next prev parent reply other threads:[~2015-11-12 20:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 17:59 [PATCH v2] cfg80211: add VHT support for Mesh Peter Oh
2015-11-12 17:59 ` Peter Oh
2015-11-12 20:03 ` Johannes Berg [this message]
2015-11-12 20:03 ` Johannes Berg
2015-11-12 21:33 ` Peter Oh
2015-11-12 21:33 ` Peter Oh
2015-11-12 21:40 ` Johannes Berg
2015-11-12 21:40 ` Johannes Berg
2015-11-12 22:28 ` Peter Oh
2015-11-12 22:28 ` Peter Oh
2015-11-12 22:32 ` Johannes Berg
2015-11-12 22:32 ` Johannes Berg
2015-11-12 23:05 ` Peter Oh
2015-11-12 23:05 ` Peter Oh
2015-11-13 7:37 ` Johannes Berg
2015-11-13 7:37 ` Johannes Berg
2015-11-13 23:50 ` Peter Oh
2015-11-13 23:50 ` Peter Oh
2015-11-15 14:38 ` Johannes Berg
2015-11-15 14:38 ` 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=1447358605.2131.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=poh@qca.qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.