From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] wireless: Support can-scan-one logic.
Date: Wed, 18 May 2011 16:30:36 -0700 [thread overview]
Message-ID: <4DD4569C.7080303@candelatech.com> (raw)
In-Reply-To: <1305759738.8827.6.camel@jlt3.sipsolutions.net>
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.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-18 23:30 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 [this message]
2011-06-02 19:12 ` Luis R. Rodriguez
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=4DD4569C.7080303@candelatech.com \
--to=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 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.