From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: [PATCH 0/3] rt2x00
Date: Mon, 12 Nov 2007 15:02:01 +0100 [thread overview]
Message-ID: <200711121502.01953.IvDoorn@gmail.com> (raw)
Hi John,
Here is a minor update for rt2x00, no version bump this time since
the number of patches is so limited. If possible queue these for 2.6.24.
The first one fixes a bug in the chipset revision detection, where devices
were being accepted by the rt2500usb driver while they should be dropped
(in favour of rt73usb).
The second patch is code cleaning, but the third patch depends on this one.
Finally the first patch fixes the dreadfull "non-free entry in the non-full queue"
queue messages which effectively resulted in the TX shutting down comlpletely
with rt61pci.
Ivo
next reply other threads:[~2007-11-12 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 14:02 Ivo van Doorn [this message]
2007-11-12 14:02 ` [PATCH 1/3] rt2x00: Fix chipset revision validation Ivo van Doorn
2007-11-12 14:02 ` [PATCH 2/3] rt2x00: Move duplicate code into rt2x00pci_txdone() Ivo van Doorn
2007-11-12 14:03 ` [PATCH 3/3] rt2x00: Allow rt61 to catch up after a missing tx report Ivo van Doorn
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=200711121502.01953.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.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).