From: Christoph Hellwig <firstname.lastname@example.org>
To: Andrew Vasquez <email@example.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Linux Kernel <firstname.lastname@example.org>,
Subject: Re: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7).
Date: Thu, 8 Jan 2004 16:54:14 +0000 [thread overview]
Message-ID: <20040108165414.A12233@infradead.org> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B060EDD4@AVEXCH02.qlogic.org>; from email@example.com on Thu, Jan 08, 2004 at 08:47:51AM -0800
On Thu, Jan 08, 2004 at 08:47:51AM -0800, Andrew Vasquez wrote:
> Yes, given the structure and form of recent patches, that certainly
> does seem to be the case - which from QLogic's standpoint (now) seems
> to be the proper path. Just for clarification, given the structure of
> the driver now (failover completely separated), inclusion of the
> qla2xxx driver would exclude the following failover files:
> qla_fo.c qla_foln.c qla_cfg.c qla_cfgln.c
+ qla_inioct.c qla_xioct.c
and the associated headers for both the ioctl and failover code, of course
> > - The odd ioctl set to the qla device...I'd much rather see something
> > more standard that all FC drivers can use.
> Are you proposing to standardize a transport by which a user-space
> application communicates with a driver (beyond IOCTLs), or, are you
> suggesting there be some commonality in functional interfaces (i.e.
> SNIA) for all FC drivers?
the SNIA HBA-API spec is completely broken. But we should try to support
a sanitized subset of the spec using the transport class work that's
currently discussed on linux-scsi.
next prev parent reply other threads:[~2004-01-08 16:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 16:47 [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7) Andrew Vasquez
2004-01-08 16:54 ` Christoph Hellwig [this message]
2004-01-08 19:33 ` Mike Anderson
2004-01-08 19:34 ` Christoph Hellwig
2004-01-08 19:57 ` Mike Anderson
2004-01-08 20:06 ` Christoph Hellwig
2004-01-08 22:11 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 19:29 Andrew Vasquez
2003-12-06 1:15 Andrew Vasquez
2003-12-09 13:28 ` Christoph Hellwig
2003-12-29 17:32 ` James Bottomley
2003-12-05 20:52 Andrew Vasquez
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).