linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [wireless-next PATCH 2/5] wifi: Support disabling ht40.
Date: Fri, 28 Oct 2011 09:25:51 -0700	[thread overview]
Message-ID: <4EAAD78F.8000009@candelatech.com> (raw)
In-Reply-To: <1319789370.3914.11.camel@jlt3.sipsolutions.net>

On 10/28/2011 01:09 AM, Johannes Berg wrote:
> On Thu, 2011-10-27 at 22:11 -0700, greearb@candelatech.com 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2011-10-28 16:25 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28  5:11 [wireless-next PATCH 1/5] mac80211: Support forcing station to disable 11n greearb
2011-10-28  5:11 ` [wireless-next PATCH 2/5] wifi: Support disabling ht40 greearb
2011-10-28  8:09   ` Johannes Berg
2011-10-28 16:25     ` Ben Greear [this message]
2011-10-28  5:11 ` [wireless-next PATCH 3/5] wifi: Allow overriding some HT information greearb
2011-10-28  8:12   ` Johannes Berg
2011-10-28 16:33     ` Ben Greear
2011-11-02  8:13       ` Johannes Berg
2011-11-02 16:59         ` Ben Greear
2011-11-02 17:49           ` Johannes Berg
2011-11-02 18:03             ` Ben Greear
2011-11-03  8:32               ` Johannes Berg
2011-10-28  5:11 ` [wireless-next PATCH 4/5] wifi: Warn if cannot add station debugfs entries greearb
2011-10-28  8:13   ` Johannes Berg
2011-10-28 16:13     ` Ben Greear
2011-10-28  5:11 ` [wireless-next PATCH 5/5] wifi-debugfs: Fix AMSDU rate printout greearb
2011-10-28  8:13   ` Johannes Berg
2011-11-17 17:49   ` Ben Greear
2011-11-17 18:03     ` John W. Linville
2011-10-28  5:15 ` [wireless-next PATCH 1/5] mac80211: Support forcing station to disable 11n Ben Greear
2011-10-28  8:08 ` Johannes Berg
2011-10-28 16:24   ` Ben Greear
2011-11-02  7:56     ` Johannes Berg
2011-11-02 16:37       ` Ben Greear
2011-10-28 18:55   ` Ben Greear
2011-11-02  7:53     ` Johannes Berg
2011-11-02 16:34       ` Ben Greear
2011-11-02 17:51         ` Johannes Berg
2011-11-03  6:04           ` Ben Greear
2011-11-03  8:30             ` Johannes Berg
2011-11-03 18:17               ` Ben Greear
2011-11-04 14:42                 ` Johannes Berg
2011-11-04 16:11                   ` Ben Greear
2011-11-04 16:17                     ` Johannes Berg

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=4EAAD78F.8000009@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 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).