From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH net-2.6.24] cfg80211: use idr layer for wiphy indizes
Date: Thu, 06 Sep 2007 19:56:56 +0200 [thread overview]
Message-ID: <1189101416.28781.115.camel@johannes.berg> (raw)
In-Reply-To: <1188480704.2963.41.camel@johannes.berg>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Thu, 2007-08-30 at 15:31 +0200, Johannes Berg wrote:
> This makes cfg80211 use the idr layer instead of keeping
> an own list of registered devices.
Hmm. Come to think of it, this is not good as it makes us reuse the
wiphy numbers. Normally that would be fine, however, here it would
probably be nicer for tools to know that a specific wiphy no longer
exists when they have an old index.
Please don't apply. I'll make a new patch to still keep a list but
introduce the walking helper.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-09-07 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 13:31 [PATCH net-2.6.24] cfg80211: use idr layer for wiphy indizes Johannes Berg
2007-09-06 17:56 ` 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=1189101416.28781.115.camel@johannes.berg \
--to=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