linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@gmail.com>
To: John W Linville <linville@tuxdriver.com>
Cc: <linux-wireless@vger.kernel.org>, <users@rt2x00.serialmonkey.com>,
	Ivo van Doorn <IvDoorn@gmail.com>,
	Helmut Schaa <helmut.schaa@googlemail.com>,
	Gertjan van Wingerde <gwingerde@gmail.com>
Subject: [PATCH 0/7] Assorted fixes and clean-ups.
Date: Wed, 28 Dec 2011 01:53:17 +0100	[thread overview]
Message-ID: <1325033604-26469-1-git-send-email-gwingerde@gmail.com> (raw)

Assorted fixes and clean-ups for rt2x00.

Note these patches are on top of Larry Finger's uncommitted patch in
http://marc.info/?l=linux-wireless&m=132501461624898&w=2

Gertjan van Wingerde (6):
  rt2x00: Identify rt2800usb chipsets.
  rt2x00: Whitespace cleanup.
  rt2x00: Convert big if-statements to switch-statements.
  rt2x00: RT3593 is also applicable to USB.
  rt2x00: Change RF3853 to RF3053.

Jakub Kiciński (2):
  rt2800usb: Let rt2x00usb handle USB padding
  rt2x00usb: Zero USB padding before sending URB

 drivers/net/wireless/rt2x00/rt2800.h    |    4 +-
 drivers/net/wireless/rt2x00/rt2800lib.c |   55 ++++++++++++++++----------
 drivers/net/wireless/rt2x00/rt2800usb.c |   65 +++++++++++--------------------
 drivers/net/wireless/rt2x00/rt2x00.h    |    4 +-
 drivers/net/wireless/rt2x00/rt2x00usb.c |   16 ++++++-
 5 files changed, 74 insertions(+), 70 deletions(-)

-- 
1.7.7.4


             reply	other threads:[~2011-12-28  0:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28  0:53 Gertjan van Wingerde [this message]
2011-12-28  0:53 ` [PATCH 1/7] rt2x00: Identify rt2800usb chipsets Gertjan van Wingerde
2011-12-28  0:53   ` [PATCH 2/7] rt2x00: Whitespace cleanup Gertjan van Wingerde
2011-12-28  0:53     ` [PATCH 3/7] rt2x00: Convert big if-statements to switch-statements Gertjan van Wingerde
2011-12-28  0:53       ` [PATCH 4/7] rt2800usb: Let rt2x00usb handle USB padding Gertjan van Wingerde
2011-12-28  0:53         ` [PATCH 5/7] rt2x00usb: Zero USB padding before sending URB Gertjan van Wingerde
2011-12-28  0:53           ` [PATCH 6/7] rt2x00: RT3593 is also applicable to USB Gertjan van Wingerde
2011-12-28  0:53             ` [PATCH 7/7] rt2x00: Change RF3853 to RF3053 Gertjan van Wingerde
2011-12-28 20:12               ` Ivo Van Doorn
2011-12-28 20:12             ` [PATCH 6/7] rt2x00: RT3593 is also applicable to USB Ivo Van Doorn
2011-12-28 22:40           ` [PATCH 5/7] rt2x00usb: Zero USB padding before sending URB Ivo Van Doorn
2011-12-28 20:12         ` [PATCH 4/7] rt2800usb: Let rt2x00usb handle USB padding Ivo Van Doorn
2011-12-28 20:43           ` Gertjan van Wingerde
2011-12-28 22:01             ` Andreas Hartmann
2011-12-28 22:40               ` Ivo Van Doorn
2011-12-28 22:40         ` Ivo Van Doorn
2011-12-28 20:11       ` [PATCH 3/7] rt2x00: Convert big if-statements to switch-statements Ivo Van Doorn
2011-12-28 20:10     ` [PATCH 2/7] rt2x00: Whitespace cleanup Ivo Van Doorn
2011-12-28 20:10   ` [PATCH 1/7] rt2x00: Identify rt2800usb chipsets 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=1325033604-26469-1-git-send-email-gwingerde@gmail.com \
    --to=gwingerde@gmail.com \
    --cc=IvDoorn@gmail.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=users@rt2x00.serialmonkey.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).