All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 07/13 v2] o11s: changes to ieee80211_sta
Date: Mon, 25 Feb 2008 12:49:40 -0800	[thread overview]
Message-ID: <1203972580.6929.74.camel@localhost> (raw)
In-Reply-To: <1203697317.7082.68.camel@johannes.berg>

On Fri, 2008-02-22 at 17:21 +0100, Johannes Berg wrote:
> > +	atomic_inc(&bss->users);
> > +	atomic_inc(&bss->users);
> 
> ?
> That was just allocated, shouldn't it just be atomic_set() then? And why
> two anyway?

I was following the behavior in ieee80211_rx_bss_add(), where the same
thing is done. It is needed to to avoid the bss being freed on the next
ieee80211_rx_bss_put(), works as a reference count. Agree that
atomic_set() would be better.


> > +			memset(&iwe, 0, sizeof(iwe));
> > +			iwe.cmd = IWEVCUSTOM;
> > +			sprintf(buf, "Mesh network (version %d)\n"
> > +			"\t\t\tPath Selection Protocol ID: 0x%02X%02X%02X%02X\n"
> > +			"\t\t\tPath Selection Metric ID: 0x%02X%02X%02X%02X\n"
> > +			"\t\t\tCongestion Control Mode ID: 0x%02X%02X%02X%02X\n"
> > +			"\t\t\tChannel Precedence: 0x%02X%02X%02X%02X",
> 
> Maybe we should add separate items for this to make it easier to parse
> them?

Ok, will include that too.

-- 
Luis Carlos Cobo Rus       GnuPG ID: 44019B60
cozybit Inc.



  reply	other threads:[~2008-02-25 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22  4:15 [PATCH 07/13 v2] o11s: changes to ieee80211_sta Luis Carlos Cobo
2008-02-22 16:21 ` Johannes Berg
2008-02-25 20:49   ` Luis Carlos Cobo [this message]
2008-02-25 20:49     ` Johannes Berg
2008-02-25 20:56       ` Luis Carlos Cobo
2008-02-25 20:56         ` 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=1203972580.6929.74.camel@localhost \
    --to=luisca@cozybit.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.