linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Randolf <br1@einfach.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3] mac80211: Add WME information element for IBSS
Date: Tue, 5 Oct 2010 10:24:56 +0900	[thread overview]
Message-ID: <201010051024.56936.br1@einfach.org> (raw)
In-Reply-To: <1286191300.3620.2.camel@jlt3.sipsolutions.net>

On Mon October 4 2010 20:21:40 Johannes Berg wrote:
> On Mon, 2010-10-04 at 11:17 +0900, Bruno Randolf wrote:
> > Enable WME QoS in IBSS mode by adding a WME information element to
> > beacons and probe respones and by checking for it and marking stations
> > as WME capable if it is present.
> > 
> > Signed-off-by: Bruno Randolf <br1@einfach.org>
> > 
> > ---
> > v3: use GFP_ATOMIC and re-organize nesting of "if" statements. allthough
> > in practice we would probaby always have the rates element i think it's
> > more correct to code it like this.
> 
> You're probably right, but shouldn't that be a separate patch? It
> doesn't relate to WME at all, afaict.

it does. before we only looked at elems->supp_rates, so it was o.k. to combine 
that check into the first if (adhoc mode && bssid matches). now we also check 
elems->wmm_info so we should make separate cases for each. as i noted, it 
probably does not matter much in practice, since elems->supp_rates should be 
present in all proper beacons and probe responses.

bruno

  reply	other threads:[~2010-10-05  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04  2:17 [PATCH v3] mac80211: Add WME information element for IBSS Bruno Randolf
2010-10-04 11:21 ` Johannes Berg
2010-10-05  1:24   ` Bruno Randolf [this message]
2010-10-05 20:25     ` 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=201010051024.56936.br1@einfach.org \
    --to=br1@einfach.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).