From: Pavel Roskin <proski@gnu.org>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Ivo van Doorn <ivdoorn@gmail.com>,
linux-wireless@vger.kernel.org, users@rt2x00.serialmonkey.com
Subject: Re: [PATCH 0/3] rt2x00: rt2800 detection improvements.
Date: Sat, 13 Feb 2010 20:37:31 -0500 [thread overview]
Message-ID: <1266111451.32423.14.camel@mj> (raw)
In-Reply-To: <1266090949-5468-1-git-send-email-gwingerde@gmail.com>
On Sat, 2010-02-13 at 20:55 +0100, Gertjan van Wingerde wrote:
> Some general rt2800 detection improvements. This make SOC a special
> interface, and thus simplifying SOC detection a bit, and unifies
> rt2800pci and rt2800usb further in detecting with what kind of
> rt2800 device we are dealing with.
>
> Gertjan van Wingerde (3):
> rt2x00: Introduce SoC interface type.
> rt2x00: Reorganize RT chipset setting for PCI/SOC devices.
> rt2x00: rework RT chipset and revision determination for PCI an SOC
> devices.
Rested-by: Pavel Roskin <proski@gnu.org>
Tested with rt73usb and rt2800pci. wpa_supplicant is working fine. No
new sparse warnings are introduced.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2010-02-14 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 19:55 [PATCH 0/3] rt2x00: rt2800 detection improvements Gertjan van Wingerde
2010-02-13 19:55 ` [PATCH 1/3] rt2x00: Introduce SoC interface type Gertjan van Wingerde
2010-02-13 19:55 ` [PATCH 2/3] rt2x00: Reorganize RT chipset setting for PCI/SOC devices Gertjan van Wingerde
2010-02-13 19:55 ` [PATCH 3/3] rt2x00: rework RT chipset and revision determination for PCI an SOC devices Gertjan van Wingerde
2010-02-14 1:15 ` Ivo van Doorn
2010-02-14 1:15 ` [PATCH 2/3] rt2x00: Reorganize RT chipset setting for PCI/SOC devices Ivo van Doorn
2010-02-14 1:36 ` Pavel Roskin
2010-02-14 9:21 ` Gertjan van Wingerde
2010-02-14 1:15 ` [PATCH 1/3] rt2x00: Introduce SoC interface type Ivo van Doorn
2010-02-14 1:37 ` Pavel Roskin [this message]
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=1266111451.32423.14.camel@mj \
--to=proski@gnu.org \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.