From: Bob Copeland <me@bobcopeland.com>
To: linville@tuxdriver.com, jirislaby@gmail.com, mickflemm@gmail.com,
lrodriguez@atheros.com
Cc: linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org,
Bob Copeland <me@bobcopeland.com>
Subject: [PATCH 0/5] misc ath5k fixes
Date: Wed, 15 Apr 2009 07:57:31 -0400 [thread overview]
Message-ID: <1239796656-20646-1-git-send-email-me@bobcopeland.com> (raw)
Here are various fixes for ath5k. Patch 1 is the result of a script to
compare our initval tables against the ones in the open source HALs.
Patches 2 and 3 are self-explanatory. Patches 4 and 5 may help make a
use-after-free bug more rare (though it isn't fully solved - both need
some testing so are 2.6.31 material).
Bob Copeland (5):
ath5k: fix initvals errors
ath5k: use tasklet_hi_schedule for beacon queue
ath5k: use bool for modparams
ath5k: use rx hw descriptor pointer for self-linked check
ath5k: manipulate rxlink and descriptor address under rxbuf lock
drivers/net/wireless/ath/ath5k/base.c | 35 +++++++---------------------
drivers/net/wireless/ath/ath5k/base.h | 1 -
drivers/net/wireless/ath/ath5k/dma.c | 2 -
drivers/net/wireless/ath/ath5k/initvals.c | 8 ++----
4 files changed, 12 insertions(+), 34 deletions(-)
next reply other threads:[~2009-04-15 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 11:57 Bob Copeland [this message]
2009-04-15 11:57 ` [PATCH 1/5] ath5k: fix initvals errors Bob Copeland
2009-04-15 12:09 ` Nick Kossifidis
2009-04-15 11:57 ` [PATCH 2/5] ath5k: use tasklet_hi_schedule for beacon queue Bob Copeland
2009-04-15 12:11 ` Nick Kossifidis
2009-04-15 11:57 ` [PATCH 3/5] ath5k: use bool for modparams Bob Copeland
2009-04-15 12:11 ` Nick Kossifidis
2009-04-15 11:57 ` [PATCH 4/5] ath5k: use rx hw descriptor pointer for self-linked check Bob Copeland
2009-04-15 12:12 ` Nick Kossifidis
2009-04-15 12:20 ` [ath5k-devel] " Daniel J Blueman
2009-04-15 12:35 ` Bob Copeland
2009-04-15 11:57 ` [PATCH 5/5] ath5k: manipulate rxlink and descriptor address under rxbuf lock Bob Copeland
2009-04-15 12:13 ` 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=1239796656-20646-1-git-send-email-me@bobcopeland.com \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mickflemm@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