From: Johannes Berg <johannes@sipsolutions.net>
To: Denis Kenzior <denkenz@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: FYI: vendor specific nl80211 API upstream
Date: Wed, 29 May 2019 11:09:07 +0200 [thread overview]
Message-ID: <f3847d4efe6822bba3948993ddc4cde31615436f.camel@sipsolutions.net> (raw)
In-Reply-To: <c7912523-ef79-9ac2-c465-80de189551a6@gmail.com> (sfid-20190528_193645_252220_40C340E7)
On Tue, 2019-05-28 at 12:36 -0500, Denis Kenzior wrote:
>
> I'm guessing that you guys considered and rejected the idea of pushing
> these out to a separate, vendor specific genl family instead?
We do actually use that internally (though mostly for cases where we
don't have a cfg80211 connection like manufacturing support), but vendor
commands are there and people do like to use them :-)
The idea with formalizing this is that they actually get more
visibility, and I hope that this will lead to more forming of real
nl80211 API too.
johannes
next prev parent reply other threads:[~2019-05-29 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 11:51 FYI: vendor specific nl80211 API upstream Johannes Berg
2019-05-28 17:36 ` Denis Kenzior
2019-05-29 9:09 ` Johannes Berg [this message]
2019-05-29 15:49 ` Denis Kenzior
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=f3847d4efe6822bba3948993ddc4cde31615436f.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=denkenz@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