From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: nl80211 feature flags
Date: Wed, 17 Dec 2014 21:21:43 +0100 [thread overview]
Message-ID: <1418847703.2135.28.camel@sipsolutions.net> (raw)
In-Reply-To: <5491E256.40302@broadcom.com>
On Wed, 2014-12-17 at 21:06 +0100, Arend van Spriel wrote:
> I intended to add a feature flag, but it seems filled up completely on
> mac80211-next tree. Did you already have an idea how to extend this?
Yeah, I noticed that before, but I didn't have a plan yet.
I think since the features are documented as a u32 attribute we can't
extend them very well. I think we probably have to add another attribute
- but maybe we should define the new one as a u8 array or so to begin
with (like e.g. the extended capabilities information element)
johannes
next prev parent reply other threads:[~2014-12-17 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:06 nl80211 feature flags Arend van Spriel
2014-12-17 20:21 ` Johannes Berg [this message]
2014-12-17 20:38 ` Arend van Spriel
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=1418847703.2135.28.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.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;
as well as URLs for NNTP newsgroup(s).