From: Christoph Hellwig <hch@infradead.org>
To: David.Egolf@Bull.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [(re)Announce] Emulex LightPulse Device Driver
Date: Thu, 13 May 2004 22:26:18 +0100 [thread overview]
Message-ID: <20040513222618.A16617@infradead.org> (raw)
In-Reply-To: <OF43CA8574.3A9C651D-ON07256E93.00714C91-07256E93.0075513F@az05.bull.com>; from David.Egolf@Bull.com on Thu, May 13, 2004 at 02:21:24PM -0700
On Thu, May 13, 2004 at 02:21:24PM -0700, David.Egolf@Bull.com wrote:
> The first bullet on your post is of interest to us. We currently support
> customers with Emulex fc cards using a 2.4 kernel on IA64. Our software
> employs the hba api supplied from Emulex in order determine the
> configuration of the SAN(s) connected to the cards.
>
> Your comment is on the terse side. Is your comment directed at this
> particular implementation of the hba api code, the current packaging
> situation, or do you have a general disregard for the hba api strategy? In
> short, do you believe that the hba api can and/or should be supported for
> the Emulex LightPulse Device Driver?
The SNIA HBA API is horrible interface, and we won't support it as a mean
to interact with the kernel. We're looking into a common API for quering
attributes of FC HBAs using sysfs and the fc transport class.
If someone wants to build a HBA API library ontop of that - we'll not my
business.
next prev parent reply other threads:[~2004-05-13 21:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 21:21 [(re)Announce] Emulex LightPulse Device Driver David.Egolf
2004-05-13 21:26 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-18 13:09 Smart, James
2004-05-18 13:08 Smart, James
2004-05-18 13:04 Smart, James
2004-05-18 13:07 ` 'Christoph Hellwig'
2004-05-18 13:00 Smart, James
2004-05-17 21:25 Smart, James
2004-05-18 9:58 ` 'Christoph Hellwig'
2004-05-14 19:51 Smart, James
2004-05-14 20:03 ` 'Christoph Hellwig'
2004-05-10 16:47 Smart, James
2004-05-09 4:33 Smart, James
2004-05-09 8:20 ` Christoph Hellwig
2004-05-09 8:51 ` Christoph Hellwig
2004-05-10 16:34 ` Matthew Wilcox
2004-05-18 11:59 ` Christoph Hellwig
2004-05-18 12:08 ` Christoph Hellwig
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=20040513222618.A16617@infradead.org \
--to=hch@infradead.org \
--cc=David.Egolf@Bull.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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