linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Linux-SCSI <linux-scsi@vger.kernel.org>
Subject: Re: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7).
Date: Thu, 8 Jan 2004 11:33:36 -0800	[thread overview]
Message-ID: <20040108193336.GB10243@beaverton.ibm.com> (raw)
In-Reply-To: <20040108165414.A12233@infradead.org>

Christoph Hellwig [hch@infradead.org] wrote:
> 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.
> 

This sounds good. It would seem that HBA API adapter and port
information through sysfs (libsysfs) should be doable through the
transport class.  Also some partial information of the other hba api
functions could be supported though other sysfs attributes but the sends
would still need to use the old interface.

-andmike
--
Michael Anderson
andmike@us.ibm.com


  reply	other threads:[~2004-01-08 19:31 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
2004-01-08 19:33   ` Mike Anderson [this message]
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

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=20040108193336.GB10243@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=hch@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).