On 10/28/2011 01:09 AM, Johannes Berg wrote:
On Thu, 2011-10-27 at 22:11 -0700, greearb@xxxxxxxxxxxxxxx wrote:
struct vif_params {
int use_4addr;
int disable_11n;
+ int disable_ht40;
};
All the comments on patch 1 apply -- per connection parameter,
capability flag etc.
I do wonder if it would be worthwhile to make it a u32 "connection
flags" or so instead of defining them separately.
I don't care either way. If you want a single variable to hold
the flags that is easy enough. We'd need to pass in a mask to
allow user-space to change only a subset of flags at a time
though.
Thanks,
Ben
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc http://www.candelatech.com
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html