All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@codeaurora.org>, linux-wireless@vger.kernel.org
Subject: Re: nl80211 vendor commands on upstream drivers
Date: Wed, 17 May 2017 15:34:29 +0200	[thread overview]
Message-ID: <1495028069.2442.17.camel@sipsolutions.net> (raw)
In-Reply-To: <87wp9mp4hz.fsf@kamboji.qca.qualcomm.com> (sfid-20170512_155201_855594_38A6052A)

On Fri, 2017-05-12 at 16:51 +0300, Kalle Valo wrote:
> 
> But this does not mean that the gates are open for all possible hacks
> via vendor commands, we still want to have generic nl80211 interface
> for all normal functionality. Just to give some examples of something
> which is NOT acceptable:

[snip scanning]

> * power save settings
> * btcoex settings

I'm starting to think that these might really be a vendor API for
anything but the most basic features - there's so much variation here
now.

OTOH, much of these shouldn't really be something the user needs to
twiddle with anyway.

> Comments? Am I forgetting something from the discussion?

I think that's a good summary.

johannes

  reply	other threads:[~2017-05-17 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12 13:51 nl80211 vendor commands on upstream drivers Kalle Valo
2017-05-17 13:34 ` Johannes Berg [this message]
2017-05-18  6:40   ` Kalle Valo

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=1495028069.2442.17.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=kvalo@codeaurora.org \
    --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 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.