From: Johannes Berg <johannes@sipsolutions.net>
To: "Sumangala, Suraj" <surajs@qca.qualcomm.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
ath6kl-devel <ath6kl-devel@qualcomm.com>,
"Balasubramanian, senthilkumar" <senthilb@qca.qualcomm.com>,
"Mehta, Vipin" <vipimeht@qca.qualcomm.com>,
"Valo, Kalle" <kvalo@qca.qualcomm.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [RFC] nl80211: Added NL80211 commands for Bluetooth-WiFi coex
Date: Wed, 31 Aug 2011 08:40:32 +0200 [thread overview]
Message-ID: <1314772832.4161.16.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <480687D4EEFE7447A2E09AADFF6673621AF7CDCF@nasanexd02a.na.qualcomm.com>
On Wed, 2011-08-31 at 06:36 +0000, Sumangala, Suraj wrote:
> Hi johannes,
> ???
> Why would this need a userspace utility? Are you cloning some sort of
> windows architecture here?
Ugh, please trim your quotes and use a useful mailer that will indent things.
> It will be the userpace bluez dbus events that can provide information
> regarding the status of variout Bluetooth events.
> On receiving that information, it can send corresponding NL80211
> command.
Doesn't the kernel's bluetooth subsystem already know anyway?
johannes
next prev parent reply other threads:[~2011-08-31 6:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 6:25 [RFC] nl80211: Added NL80211 commands for Bluetooth-WiFi coex Suraj Sumangala
2011-08-31 6:30 ` Johannes Berg
2011-08-31 6:36 ` Sumangala, Suraj
2011-08-31 6:40 ` Johannes Berg [this message]
2011-08-31 6:48 ` Sumangala, Suraj
2011-08-31 14:40 ` Marcel Holtmann
2011-08-31 14:56 ` Sumangala, Suraj
2011-08-31 22:51 ` Marcel Holtmann
2011-09-01 6:09 ` Sumangala, Suraj
2011-09-01 11:43 ` Marcel Holtmann
2011-09-01 12:20 ` Johannes Berg
2011-09-01 12:22 ` Kalle Valo
2011-09-02 7:54 ` Sumangala, Suraj
2011-09-02 12:04 ` Johannes Berg
2011-08-31 7:14 ` Johannes Berg
2011-08-31 14:30 ` Sumangala, Suraj
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=1314772832.4161.16.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath6kl-devel@qualcomm.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=senthilb@qca.qualcomm.com \
--cc=surajs@qca.qualcomm.com \
--cc=vipimeht@qca.qualcomm.com \
/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