From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] wireless: Support can-scan-one logic.
Date: Thu, 2 Jun 2011 12:12:14 -0700 [thread overview]
Message-ID: <BANLkTinozbG2SfOCRd1U__8-Pz9-8HCkPQ@mail.gmail.com> (raw)
In-Reply-To: <4DD4569C.7080303@candelatech.com>
On Wed, May 18, 2011 at 4:30 PM, Ben Greear <greearb@candelatech.com> wrote:
> On 05/18/2011 04:02 PM, Johannes Berg wrote:
>>
>> On Mon, 2011-05-16 at 15:51 -0700, greearb@candelatech.com wrote:
>>>
>>> From: Ben Greear<greearb@candelatech.com>
>>>
>>> Enable this by passing a -1 for a scan frequency.
>>
>> I still don't think we should do that, especially not with -1. That's
>> totally non-netlink like inband signalling. I'll also reply to your
>> other mail though since I don't think it makes sense to have this sort
>> of convenience function in the kernel.
>
> It's virtually impossible (as far as I can tell) to carry an
> out-of-tree netlink patch that uses a new netlink message
> and still keep things backwards-compat when someone adds a
> new message to the upstream kernel. So, the -1 hack works
> well for me.
>
> If it were to go into the kernel proper, then we could
> add a proper flag to the netlink API and start using
> that.
>
> If you just don't like the feature, thats OK...it is a pretty
> specialized feature, and easy enough to carry in my own tree.
Since this shit was merged can you add a respective documentation
extension for the command for nl80211.h?
Luis
next prev parent reply other threads:[~2011-06-02 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 22:51 [PATCH v2] wireless: Support can-scan-one logic greearb
2011-05-18 23:02 ` Johannes Berg
2011-05-18 23:30 ` Ben Greear
2011-06-02 19:12 ` Luis R. Rodriguez [this message]
2011-06-02 19:14 ` Johannes Berg
2011-06-02 19:15 ` Luis R. Rodriguez
2011-06-02 19:15 ` Ben Greear
2011-06-02 19:16 ` Luis R. Rodriguez
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=BANLkTinozbG2SfOCRd1U__8-Pz9-8HCkPQ@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=greearb@candelatech.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;
as well as URLs for NNTP newsgroup(s).