From: Jon Loeliger <jdl@bigfootnetworks.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Nick Kossifidis <mickflemm@gmail.com>,
Bob Copeland <bcopeland@gmail.com>, Pavel Roskin <proski@gnu.org>,
ath5k-devel@lists.ath5k.org, linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [ath5k-devel] [PATCH 1/2] ath5k: fix uninitialized value use in ath5k_eeprom_read_turbo_modes()
Date: Mon, 31 Aug 2009 10:49:55 -0500 [thread overview]
Message-ID: <1251733795.23917.1.camel@jdl-desktop> (raw)
In-Reply-To: <43e72e890908272221s39df68abq8e146c2d3566b415@mail.gmail.com>
On Thu, 2009-08-27 at 22:21 -0700, Luis R. Rodriguez wrote:
> > Having multiple drivers won't help users, i thought that MadWiFi was "dead"
> > and we were working on a complete alternative.
>
> MadWifi is dead.
>
> Luis
An interesting pronouncement. Do you mean "Dead to Linux"?
Or "Dead to the world, including FreeBSD"?
jdl
next prev parent reply other threads:[~2009-08-31 15:50 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
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 [this message]
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=1251733795.23917.1.camel@jdl-desktop \
--to=jdl@bigfootnetworks.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=bcopeland@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=mickflemm@gmail.com \
--cc=proski@gnu.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).