From: Vasanthakumar Thiagarajan <vasanth@atheros.com>
To: "greearb@gmail.com" <greearb@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Ben Greear <greearb@candelatech.com>
Subject: Re: [ath9k] ath9k: Expose virtual wiphy indexes to debugfs.
Date: Tue, 6 Jul 2010 10:29:45 +0530 [thread overview]
Message-ID: <20100706045945.GF5053@vasanth-laptop> (raw)
In-Reply-To: <1278359545-29013-1-git-send-email-greearb@candelatech.com>
On Tue, Jul 06, 2010 at 01:22:25AM +0530, greearb@gmail.com wrote:
> From: Ben Greear <greearb@candelatech.com>
>
> It is very difficult to map phyX devices to real/virtual
> entities because the phyX devices change on module
> reload. This patch makes it slightly easier to
> associate virtual phy devices with phyX entities.
>
It does not make much sense to give an index while creating a new
virtual wiphy interface. This is unncessary, only wiphy name
matters.
Vasanth
next prev parent reply other threads:[~2010-07-06 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 19:52 [ath9k] ath9k: Expose virtual wiphy indexes to debugfs greearb
2010-07-06 4:59 ` Vasanthakumar Thiagarajan [this message]
2010-07-06 5:15 ` Ben Greear
2010-07-06 6:18 ` Vasanthakumar Thiagarajan
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=20100706045945.GF5053@vasanth-laptop \
--to=vasanth@atheros.com \
--cc=greearb@candelatech.com \
--cc=greearb@gmail.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 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).