From: Michael Tokarev <mjt@tls.msk.ru>
To: Ron Mercer <ron.mercer@qlogic.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] Qlogic qla3xxx driver v2.02.00-k36 for upstream inclusion.
Date: Thu, 20 Jul 2006 13:12:42 +0400 [thread overview]
Message-ID: <44BF490A.8040604@tls.msk.ru> (raw)
In-Reply-To: <44BE98E5.7060207@garzik.org>
By the way, should it work with ISP4010 controllers?
Those "expose" network interface card "subdevice" too,
but aren't listed in pci_device_table of the driver,
and after adding the device ID to the driver, it still
does not quite work (I tried, just out of curiosity) -
the NIC on ISP4010 is - it seems - close but not exactly
the same as the driver expects.
Thanks.
/mjt
next prev parent reply other threads:[~2006-07-20 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1090CAF73D6FFE4EA45395454C82937B05214A4B@AVEXCH1.qlogic.org>
[not found] ` <0BB3E5E7462EEA4295BC02D49691DC0705BC91@AVEXCH1.qlogic.org>
2006-07-19 20:41 ` [PATCH] Qlogic qla3xxx driver v2.02.00-k36 for upstream inclusion Jeff Garzik
2006-07-20 9:12 ` Michael Tokarev [this message]
2006-07-20 14:32 Ron Mercer
2006-07-20 14:50 ` Andrew Vasquez
2006-07-20 14:59 ` Michael Tokarev
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=44BF490A.8040604@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=netdev@vger.kernel.org \
--cc=ron.mercer@qlogic.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).