linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v8 2/2] mac80211:  Support ht-cap over-rides.
Date: Wed, 09 Nov 2011 09:37:12 +0100	[thread overview]
Message-ID: <1320827832.3845.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EB9B70B.6000406@candelatech.com>

On Tue, 2011-11-08 at 15:11 -0800, Ben Greear wrote:

> > Please. I'd rather go over a bit than read the above :-)
> 
> I just fixed this by using a tmp variable.  Hopefully the
> compiler is smart enough to make it disappear.

That works, yeah.

> > I really think that'd be much nicer. As it is now we have to add all
> > these checks everywhere, if we just calculate it once and then change
> > places to use it we just have to remember to use the right thing.
> 
> I'm quite nervous about attempting this change.  I'm pretty
> confident my current patch works as designed, and over all,
> it's pretty non-intrusive.  I am afraid that if I start trying
> to substitute something for sband->ht_cap that I'm going
> to end up changing a lot of code and possibly adding all sorts
> of strange bugs.

You should only have to change the places where you now added the
overrides, no?

> Out of curiousity, if one is doing off-channel work, wouldn't
> sband be different from when we associated and possibly different
> in it's ht-capabilities?  If so, the used-ht-caps would not
> be valid for that work?

Well the off-channel work will be on the channel that you're going to be
using after a successful connection, so that should be OK.

I'd at least like to try. If it ends up a disaster maybe we shouldn't,
but the way you go back to the mask & set all the time makes me a bit
nervous.

johannes


  reply	other threads:[~2011-11-09  8:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 19:36 [PATCH v8 1/2] wireless: Support ht-capabilities over-rides greearb
2011-11-08 19:36 ` [PATCH v8 2/2] mac80211: Support ht-cap over-rides greearb
2011-11-08 20:09   ` Johannes Berg
2011-11-08 20:44     ` Ben Greear
2011-11-08 20:58       ` Johannes Berg
2011-11-08 21:00         ` Johannes Berg
2011-11-08 21:06         ` Ben Greear
2011-11-08 21:08           ` Johannes Berg
2011-11-08 20:12   ` Johannes Berg
2011-11-08 20:17     ` Johannes Berg
2011-11-08 20:58     ` Ben Greear
2011-11-08 21:02       ` Johannes Berg
2011-11-08 23:11         ` Ben Greear
2011-11-09  8:37           ` Johannes Berg [this message]
2011-11-10 19:25         ` Ben Greear
2011-11-17 11:28           ` Johannes Berg
2011-11-17 17:22             ` Ben Greear
2011-11-17 17:25               ` Johannes Berg
2011-11-17 17:42                 ` Ben Greear
2011-11-08 20:07 ` [PATCH v8 1/2] wireless: Support ht-capabilities over-rides 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=1320827832.3845.8.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.com \
    --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).