From: Johannes Berg <johannes@sipsolutions.net>
To: "Raja, Tamizh Chelvam" <c_traja@qti.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCHv2 3/4] cfg80211: Add Support set btcoex priority value
Date: Thu, 02 Mar 2017 14:43:18 +0100 [thread overview]
Message-ID: <1488462198.8390.16.camel@sipsolutions.net> (raw)
In-Reply-To: <b461827bad634932a8f0f3b3bfe5e6b4@aphydexm01f.ap.qualcomm.com>
>
> [Tamizh] I'm planning to do this check in iw itself and converting
> into a value,
>
> iw command will looks like below
>
> iw btcoex enable [<be> <bk> <vo> <vi> <mgmt><beacon>]
>
> If anything other than this given by user will be rejected and will
> not forward to cfg80211.
> Do you have any concern on this?
Yes, you really need to check it in cfg80211 and define the bits that
are valid in nl80211.
johannes
next prev parent reply other threads:[~2017-03-02 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 13:37 [PATCHv2 0/4] cfg80211: mac80211: BTCOEX feature support c_traja
2017-02-25 13:37 ` [PATCHv2 1/4] cfg80211: Add support to enable or disable btcoex c_traja
2017-02-25 14:48 ` kbuild test robot
2017-02-25 14:48 ` kbuild test robot
2017-03-02 8:45 ` Johannes Berg
2017-03-02 11:49 ` Raja, Tamizh Chelvam
2017-02-25 13:37 ` [PATCHv2 2/4] mac80211: " c_traja
2017-02-25 13:37 ` [PATCHv2 3/4] cfg80211: Add Support set btcoex priority value c_traja
2017-02-25 15:12 ` kbuild test robot
2017-03-02 8:50 ` Johannes Berg
2017-03-02 11:48 ` Raja, Tamizh Chelvam
2017-03-02 12:15 ` Johannes Berg
2017-03-02 13:08 ` Raja, Tamizh Chelvam
2017-03-02 13:43 ` Johannes Berg [this message]
2017-03-02 8:51 ` Johannes Berg
2017-02-25 13:37 ` [PATCHv2 4/4] mac80211: Add support to set/update " c_traja
2017-02-25 14:41 ` [PATCHv2 0/4] cfg80211: mac80211: BTCOEX feature support Arend Van Spriel
2017-02-27 10:33 ` Raja, Tamizh Chelvam
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=1488462198.8390.16.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath10k@lists.infradead.org \
--cc=c_traja@qti.qualcomm.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).