From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "John W. Linville" <linville@redhat.com>,
linux-wireless@vger.kernel.org, centos@centos.org,
ipw3945@lists.sourceforge.net, ath9k-devel@lists.ath9k.org
Subject: Re: [internal-ath9k-devel] RHEL5.5 (and Centos 5.5!) wireless updates needs broad testing...
Date: Thu, 3 Dec 2009 09:29:32 -0500 [thread overview]
Message-ID: <20091203142932.GA2835@tuxdriver.com> (raw)
In-Reply-To: <43e72e890912021450t454dc740r91ea88365779d2c6@mail.gmail.com>
On Wed, Dec 02, 2009 at 02:50:28PM -0800, Luis R. Rodriguez wrote:
> On Sat, Nov 28, 2009 at 1:21 PM, John W. Linville <linville@redhat.com> wrote:
> > If you have a wireless LAN enabled box running RHEL5 (or CentOS 5 or
> > other equivalent) then please give these kernels a try. When you find
> > problems, please open a bug against RHEL5.5 at bugzilla.redhat.com
> > and Cc: me on the bug. Remember, the surest way to avoid a bug in
> > RHEL5.5 is to find it before it is released, and the surest way to
> > avoid a bug in CentOS is to keep it out of RHEL... :-)
> >
> > I appreciate your help!
>
>
> Thanks John, I'm keeping track of ath9k issues with regards to this kernel here:
>
> http://wireless.kernel.org/en/users/Drivers/ath9k/RHEL5
>
> If anyone else finds issues please add a link there.
Cool, thanks! Also, please remember to Cc me on any new bugs...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-12-03 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 21:21 RHEL5.5 (and Centos 5.5!) wireless updates needs broad testing John W. Linville
2009-12-02 22:50 ` [internal-ath9k-devel] " Luis R. Rodriguez
2009-12-03 14:29 ` John W. Linville [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=20091203142932.GA2835@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=centos@centos.org \
--cc=ipw3945@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@redhat.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 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).