From: Chr <chunkeey@web.de>
To: linux-wireless@vger.kernel.org
Cc: Michael Wu <flamingice@sourmilk.net>
Subject: [RFC][PATCH 0/4] p54: various updates
Date: Tue, 1 Apr 2008 23:39:36 +0200 [thread overview]
Message-ID: <200804012339.37204.chunkeey@web.de> (raw)
Hi,
this is the next RFC round...
1) rename all prism54* to p54* (to match the filenames)
2) rx_tasklet for p54pci
3) link statistics
4) AP-Patch
Signed-off-by: Christian Lamparter <chunkeey@web.de>
---
diffstat:
p54.h | 40 ++++
p54common.c | 487
++++++++++++++++++++++++++++++++++++++++++++++++------------
p54common.h | 111 ++++++++++---
p54pci.c | 283 ++++++++++++++++++++++------------
p54pci.h | 20 +-
p54usb.c | 34 ++--
p54usb.h | 6
7 files changed, 726 insertions(+), 255 deletions(-)
next reply other threads:[~2008-04-01 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 21:39 Chr [this message]
2008-04-02 23:42 ` [RFC][PATCH 0/4] p54: various updates Luis R. Rodriguez
2008-04-03 15:40 ` Chr
2008-04-03 22:34 ` Luis R. Rodriguez
2008-04-04 2:07 ` Chr
2008-04-08 12:48 ` [RFC][PATCH 0/4] p54: various updates (all in one) Chr
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=200804012339.37204.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=flamingice@sourmilk.net \
--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;
as well as URLs for NNTP newsgroup(s).