From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: FYI: vendor specific nl80211 API upstream
Date: Tue, 28 May 2019 13:51:55 +0200 [thread overview]
Message-ID: <c138fac51c7f49bbcd8617ae0a2c750d78abb35d.camel@sipsolutions.net> (raw)
Hi all,
FYI - at the discussions in Prague we decided to let some vendor
specific nl80211 API go upstream, and I've just documented the expected
rules here:
https://wireless.wiki.kernel.org/en/developers/documentation/nl80211#vendor-specific_api
I guess this will be fine-tuned as we go along, but wanted all to be
aware.
johannes
next reply other threads:[~2019-05-28 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 11:51 Johannes Berg [this message]
2019-05-28 17:36 ` FYI: vendor specific nl80211 API upstream Denis Kenzior
2019-05-29 9:09 ` Johannes Berg
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=c138fac51c7f49bbcd8617ae0a2c750d78abb35d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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