From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Should we remove all the virtual wiphy code from ath9k?
Date: Thu, 20 Jan 2011 10:49:34 -0800 [thread overview]
Message-ID: <20110120184934.GE10554@tux> (raw)
In-Reply-To: <4D387E75.8000006@candelatech.com>
On Thu, Jan 20, 2011 at 10:27:01AM -0800, Ben Greear wrote:
> Seems I saw a note a long time ago about virtual wiphy being
> removed sometime soon. Should we go ahead and remove it?
>
> It doesn't seem useful to me (virtual interfaces appear to
> work much better), and it would likely simplify the code
> a bit to have it gone.
As much as I love the funcitonality it complicates the driver,
and I would welcome the rm -rf of it given that experimenters
can simply use older kernels now with the virtual wiphy.
Jouni, thoughts?
Luis
prev parent reply other threads:[~2011-01-20 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 18:27 [ath9k-devel] Should we remove all the virtual wiphy code from ath9k? Ben Greear
2011-01-20 18:42 ` Jouni Malinen
2011-01-20 18:49 ` Luis R. Rodriguez [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=20110120184934.GE10554@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.