From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] cfg80211: refactor hidden SSID finding
Date: Mon, 04 Feb 2013 16:39:10 +0100 [thread overview]
Message-ID: <1359992350.10311.17.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1359503120-25685-1-git-send-email-johannes@sipsolutions.net> (sfid-20130130_004508_523732_488C5419)
On Wed, 2013-01-30 at 00:45 +0100, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> Instead of duplicating the rbtree functions, pass
> an argument to the compare function. This removes
> the code duplication for the two searches.
Applied (the version with the !ie1 && !ie2 fix)
johannes
prev parent reply other threads:[~2013-02-04 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:45 [PATCH 1/2] cfg80211: refactor hidden SSID finding Johannes Berg
2013-01-29 23:45 ` [PATCH 2/2] cfg80211: simplify mesh BSS comparison Johannes Berg
2013-01-30 1:42 ` Thomas Pedersen
2013-01-30 7:49 ` Johannes Berg
2013-01-29 23:55 ` [PATCH 1/2] cfg80211: refactor hidden SSID finding Johannes Berg
2013-02-04 15:39 ` Johannes Berg [this message]
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=1359992350.10311.17.camel@jlt4.sipsolutions.net \
--to=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).