From: "John W. Linville" <linville@tuxdriver.com>
To: Steven Noonan <steven@uplinklabs.net>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
Howard Chu <hyc@symas.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k problems
Date: Mon, 22 Sep 2008 15:47:39 -0400 [thread overview]
Message-ID: <20080922194739.GB3660@tuxdriver.com> (raw)
In-Reply-To: <f488382f0809220021qc1a3abatada16972eea1d44c@mail.gmail.com>
On Mon, Sep 22, 2008 at 12:21:52AM -0700, Steven Noonan wrote:
> On Sun, Sep 21, 2008 at 11:48 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> >> but wireless-testing is pretty outdated
> >
> > This is not accurate.
> >
> > It lacks new patches from Linus' tree, but it has the latest
> > and greatest possible wireless patches. John maintains Linux
> > wireless so he'll always have more updated patches for wireless than
> > Linus.
> >
>
> I've had much less luck running wireless-testing than I have had
> running -tip or Linus' trees. Perhaps it -is- inaccurate that it's
> outdated, but it's certainly less usable, from what I've seen.
The wireless-testing tree is based on an -rc from Linus plus any later
wireless patches (minus whatever is still sitting in my mailbox at
the time). If it is less usable, it is either due to some wireless
breakage (send us bug reports) or Linus is producing crap -rc releases
(possible).
Current wireless-testing is based on 2.6.27-rc6. Since -rc7 just
came-out yesterday...
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-09-22 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 4:17 ath9k problems Howard Chu
2008-09-21 4:22 ` Steven Noonan
2008-09-22 6:48 ` Luis R. Rodriguez
2008-09-22 7:21 ` Steven Noonan
2008-09-22 8:08 ` Luis R. Rodriguez
2008-09-22 19:47 ` John W. Linville [this message]
2008-09-22 9:09 ` Howard Chu
2008-09-22 9:45 ` Luis R. Rodriguez
2008-09-22 11:31 ` Howard Chu
2008-09-22 17:30 ` Luis R. Rodriguez
2008-09-22 20:34 ` Howard Chu
2008-09-22 21:16 ` 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=20080922194739.GB3660@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=hyc@symas.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=steven@uplinklabs.net \
/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).