From: Felix Fietkau <nbd@openwrt.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
ic.felix@gmail.com
Subject: Re: [ath5k-devel] [PATCH 1/2] ath5k: fix uninitialized value use in ath5k_eeprom_read_turbo_modes()
Date: Sat, 29 Aug 2009 03:35:24 +0200 [thread overview]
Message-ID: <4A9885DC.4030105@openwrt.org> (raw)
In-Reply-To: <20090828154410.GB32694@tuxdriver.com>
John W. Linville wrote:
> I think I am on the side of removing the non-standard extensions.
> FWIW, I'll need a patch posted with a proper Subject and
> Signed-off-by...
>
> I think Nick has some valid points. His position sounds similar to
> that expressed to me by Felix and some others that it would be nice
> if we could more easily accomodate some of the features of madwifi
> that have made it attractive to researchers and experimenters.
> Perhaps NL80211_CMD_TESTMODE relates to this desire?
Yes, that would be a good solution. I know a lot of people who are going
continue to stick with madwifi if they won't be able to use turbo mode
with ath5k. Since quite a few of those people are using OpenWrt, it
would also mean that I would have to continue to maintain my madwifi
semi-fork in OpenWrt even longer, and I definitely want to avoid that.
- Felix
next prev parent reply other threads:[~2009-08-29 1:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 2:30 [PATCH 1/2] ath5k: fix uninitialized value use in ath5k_eeprom_read_turbo_modes() Pavel Roskin
2009-08-27 2:30 ` [PATCH 2/2] ath5k: don't use PCI ID to find the chip revision Pavel Roskin
2009-08-27 3:45 ` Bob Copeland
2009-08-27 13:10 ` [ath5k-devel] " Nick Kossifidis
2009-08-27 3:43 ` [PATCH 1/2] ath5k: fix uninitialized value use in ath5k_eeprom_read_turbo_modes() Bob Copeland
2009-08-27 12:58 ` [ath5k-devel] " Nick Kossifidis
2009-08-27 18:17 ` Bob Copeland
2009-08-27 18:25 ` Luis R. Rodriguez
2009-08-27 21:39 ` Bob Copeland
2009-08-27 23:14 ` Luis R. Rodriguez
2009-08-28 0:09 ` Luis R. Rodriguez
2009-08-28 3:06 ` Nick Kossifidis
2009-08-28 15:44 ` John W. Linville
2009-08-29 1:35 ` Felix Fietkau [this message]
2009-08-28 3:01 ` Nick Kossifidis
2009-08-28 3:57 ` Luis R. Rodriguez
2009-08-28 4:17 ` Nick Kossifidis
2009-08-28 5:21 ` Luis R. Rodriguez
2009-08-28 13:06 ` Nick Kossifidis
2009-08-31 15:49 ` Jon Loeliger
2009-08-28 3:17 ` Nick Kossifidis
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=4A9885DC.4030105@openwrt.org \
--to=nbd@openwrt.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=ic.felix@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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 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.