From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Stefan Seyfried <stefan.seyfried@googlemail.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add support for Sphairon Homelink 1202 USB WLAN
Date: Fri, 11 Dec 2009 15:55:23 +0100 [thread overview]
Message-ID: <1260543323.2442.287.camel@johannes.local> (raw)
In-Reply-To: <20091211144221.GA6663@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
On Fri, 2009-12-11 at 09:42 -0500, John W. Linville wrote:
> It strikes me as strange that you are hitting two drivers to support
> one device. Are you saying that your ar9170usb has the goofy storage
> device thing using the same USB IDs that the zd1211rw devices like that
> used? I suppose that makes some sense given the shared heritage...
Good catch -- even if ar9170 descended from zd1211 it doesn't seem
appropriate to require two drivers for a single device.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-12-11 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 14:21 [PATCH 0/2] Add support for Sphairon Homelink 1202 USB WLAN Stefan Seyfried
2009-12-08 14:21 ` [PATCH 1/2] ar9170usb: add Sphairon Homelink 1202 USB ID Stefan Seyfried
2009-12-08 14:21 ` [PATCH 2/2] zd1211rw: improve ejecting of fake CDROM Stefan Seyfried
2009-12-11 12:36 ` [PATCH 0/2] Add support for Sphairon Homelink 1202 USB WLAN Stefan Seyfried
2009-12-11 14:42 ` John W. Linville
2009-12-11 14:55 ` Johannes Berg [this message]
2009-12-11 15:05 ` Stefan Seyfried
2009-12-11 15:01 ` Stefan Seyfried
2009-12-11 19:21 ` Dan Williams
2009-12-11 22:37 ` Stefan Seyfried
2009-12-15 12:17 ` Stefan Seyfried
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=1260543323.2442.287.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stefan.seyfried@googlemail.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