Linux wireless drivers development
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: FYI: vendor specific nl80211 API upstream
Date: Tue, 28 May 2019 12:36:49 -0500	[thread overview]
Message-ID: <c7912523-ef79-9ac2-c465-80de189551a6@gmail.com> (raw)
In-Reply-To: <c138fac51c7f49bbcd8617ae0a2c750d78abb35d.camel@sipsolutions.net>

Hi Johannes,

On 05/28/2019 06:51 AM, Johannes Berg wrote:
> 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'm guessing that you guys considered and rejected the idea of pushing 
these out to a separate, vendor specific genl family instead?

Regards,
-Denis

  reply	other threads:[~2019-05-28 17:36 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 [this message]
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=c7912523-ef79-9ac2-c465-80de189551a6@gmail.com \
    --to=denkenz@gmail.com \
    --cc=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