From: Antonio Quartulli <antonio@open-mesh.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Antonio Quartulli <ordex@autistici.org>,
Johannes Berg <johannes@sipsolutions.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] nl80211: allow sending CMD_FRAME without specifying any frequency
Date: Wed, 5 Jun 2013 11:53:11 +0200 [thread overview]
Message-ID: <20130605095311.GA2349@open-mesh.com> (raw)
In-Reply-To: <877gi8khyi.fsf@kamboji.qca.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Wed, Jun 05, 2013 at 02:47:01AM -0700, Kalle Valo wrote:
> Antonio Quartulli <ordex@autistici.org> writes:
>
> > From: Antonio Quartulli <antonio@open-mesh.com>
> >
> > Users may want to send a frame on the current channel
> > without specifying it.
> >
> > Make mgmt_tx pass a NULL channel to mac80211 if none has
> > been specified by the user.
> >
> > Signed-off-by: Antonio Quartulli <antonio@open-mesh.com>
>
> Why? And what users are we talking about here? It would be nice if the
> commit log would give some context here for use who nothing about this
> patch. "Users may want" is not very informative :)
Hello Kalle,
thanks for your feedback.
Sure, I can change the commit log.
However, I already wrote a couple of (userspace) applications which wanted to
send a message on the current channel and the only way to do it was to first get
the current channel and then pass it when sending a CMD_FRAME via nl80211. Of
course this approach is just a bit racy :-)
Moreover, I'm currently working on improving IBSS/RSN support in wpa_supplicant
and sending frames on the current channel is needed.
Do you think it is worth mentioning userspace applications like wpa_s in the
kernel commit message?
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-05 10:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 6:39 [PATCH 1/2] nl80211: allow sending CMD_FRAME without specifying any frequency Antonio Quartulli
2013-06-03 6:39 ` [PATCH 2/2] mac80211: in mgmt_tx use the current channel if none has been specified Antonio Quartulli
2013-06-03 15:01 ` Johannes Berg
2013-06-03 18:03 ` Antonio Quartulli
2013-06-03 18:16 ` Johannes Berg
2013-06-03 18:26 ` Antonio Quartulli
2013-06-03 14:07 ` [PATCH 1/2] nl80211: allow sending CMD_FRAME without specifying any frequency Nicolas Cavallari
2013-06-03 14:25 ` Antonio Quartulli
2013-06-03 14:59 ` Johannes Berg
2013-06-03 15:04 ` Nicolas Cavallari
2013-06-03 17:14 ` ath6kl_mgmt_tx with NULL chan (was Re: [PATCH 1/2] nl80211: allow sending CMD_FRAME without specifying any frequency) Antonio Quartulli
2013-06-05 9:57 ` ath6kl_mgmt_tx with NULL chan Kalle Valo
2013-06-05 10:03 ` Antonio Quartulli
2013-06-05 10:15 ` Kalle Valo
2013-06-05 11:00 ` Antonio Quartulli
2013-06-05 9:47 ` [PATCH 1/2] nl80211: allow sending CMD_FRAME without specifying any frequency Kalle Valo
2013-06-05 9:53 ` Antonio Quartulli [this message]
2013-06-05 10:05 ` Kalle Valo
2013-06-05 10:08 ` Antonio Quartulli
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=20130605095311.GA2349@open-mesh.com \
--to=antonio@open-mesh.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ordex@autistici.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).