From: Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk>
To: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/2] ath5k: few AP fixes for 2.6.32
Date: Sat, 13 Mar 2010 12:52:26 +0000 [thread overview]
Message-ID: <wfiq901j05.fsf@calligramme.charmers> (raw)
In-Reply-To: 1268349829-3195-1-git-send-email-lrodriguez@atheros.com
"Luis R. Rodriguez"
<lrodriguez@atheros.com> writes:
> These patches were already merged into the latest 2.6.33.y,
> however they are not yet in the latest 2.6.32.y, they are
> reported to make ath5k AP support rock solid by a few people.
>
> For your conveinience I have also put these patches up here:
>
> http://kernel.org/pub/linux/kernel/people/mcgrof/patches/ath5k/2010-03/ath5k-ap-fixes-32/
Apologies for being ignorant of process, but which bundle of
compat-wireless do (/will?) these patches appear in, and which
version of 2.6.32 will they be in?
I'm running an ath5k AP on a 64-bit Fedora 12 system, and while
it was pretty reliable on 2.6.31, a recent update took the
version to 2.6.32 (currently running 3.6.32.9-67, and next
update is to 2.6.32.9-70 in case the Fedora version numbers make
sense to anyone reading this), and I'm getting the "no further
txbuf" issue, so I'd like to build a version of the module with
these patches, but ideally not a bleeding edge one.
Thanks,
Jón
--
Jón Fairbairn Jon.Fairbairn@cl.cam.ac.uk
next prev parent reply other threads:[~2010-03-13 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 23:23 [PATCH 0/2] ath5k: few AP fixes for 2.6.32 Luis R. Rodriguez
2010-03-11 23:23 ` [PATCH 1/2] ath5k: dont use external sleep clock in AP mode Luis R. Rodriguez
2010-03-11 23:23 ` [PATCH 2/2] ath5k: fix setup for CAB queue Luis R. Rodriguez
2010-03-13 12:52 ` Jon Fairbairn [this message]
2010-03-18 21:24 ` [stable] [PATCH 0/2] ath5k: few AP fixes for 2.6.32 Greg KH
2010-03-18 21:44 ` Luis R. Rodriguez
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=wfiq901j05.fsf@calligramme.charmers \
--to=jon.fairbairn@cl.cam.ac.uk \
--cc=linux-wireless@vger.kernel.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