LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David.Egolf@Bull.com
To: Christoph Hellwig <hch@infradead.org>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
	linux-scsi-owner@vger.kernel.org
Subject: Re: [(re)Announce] Emulex LightPulse Device Driver
Date: Thu, 13 May 2004 14:21:24 -0700	[thread overview]
Message-ID: <OF43CA8574.3A9C651D-ON07256E93.00714C91-07256E93.0075513F@az05.bull.com> (raw)

Christoph Hellwig <hch@infradead.org>
Sent by: linux-scsi-owner@vger.kernel.org
05/09/2004 01:20 AM

>A bunch of comments from looking over the headers and itnerface to
>upper layers a little:  (next I'll try to understand what's going on
>in the I/O submission path - it's just to freakin complicated..):
>
> - the hba api crap must die
> o o o

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? 

-- David Egolf

             reply	other threads:[~2004-05-13 21:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 21:21 David.Egolf [this message]
2004-05-13 21:26 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2004-05-17 21:25 Smart, James
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

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=OF43CA8574.3A9C651D-ON07256E93.00714C91-07256E93.0075513F@az05.bull.com \
    --to=david.egolf@bull.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --subject='Re: [(re)Announce] Emulex LightPulse Device Driver' \
    /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

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).