From: "John W. Linville" <linville@tuxdriver.com>
To: Ashok Nagarajan <ashok@cozybit.com>
Cc: linux-wireless@vger.kernel.org, javier@cozybit.com,
dan.carpenter@oracle.com
Subject: Re: [PATCH v4] {nl,cfg,mac}80211: Implement RSSI threshold for mesh peering
Date: Wed, 7 Mar 2012 08:56:20 -0500 [thread overview]
Message-ID: <20120307135619.GA12245@tuxdriver.com> (raw)
In-Reply-To: <20120306193350.GA3353@tuxdriver.com>
On Tue, Mar 06, 2012 at 02:33:50PM -0500, John W. Linville wrote:
> On Tue, Mar 06, 2012 at 11:23:30AM -0800, Ashok Nagarajan wrote:
> > Mesh peer links are established only if average rssi of the peer
> > candidate satisfies the threshold. This is not in 802.11s specification
> > but was requested by David Fulgham, an open80211s user. This is a way to avoid
> > marginal peer links with stations that are barely within range.
> >
> > This patch adds a new mesh configuration parameter, mesh_rssi_threshold. This
> > feature is supported only for hardwares that report signal in dBm.
> >
> > Signed-off-by: Ashok Nagarajan <ashok@cozybit.com>
> > Signed-off-by: Javier Cardona <javier@cozybit.com>
> > ---
> > v3:
> > use s32 instead of int32_t (Kalle Valo)
> > Feature to be supported for devices reporting signal in dBm (Johannes)
> >
> > v4:
> > Fix potential null pointer deferencing (Dan Carpenter)
>
> I already merged v3 yesterday -- can you rework this as a fix instead?
Mail server problems, this was delayed. I see that you already sent a new one.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-03-07 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 19:23 [PATCH v4] {nl,cfg,mac}80211: Implement RSSI threshold for mesh peering Ashok Nagarajan
2012-03-06 19:33 ` John W. Linville
2012-03-07 13:56 ` John W. Linville [this message]
2012-03-06 20:45 ` Ashok Nagarajan
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=20120307135619.GA12245@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ashok@cozybit.com \
--cc=dan.carpenter@oracle.com \
--cc=javier@cozybit.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 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.