From: Arjan van de Ven <arjan@infradead.org>
To: James.Smart@Emulex.Com
Cc: mark_salyzyn@adaptec.com, Luben_Tuikov@adaptec.com,
andrew.patterson@hp.com, dougg@torque.net, torvalds@osdl.org,
ltuikov@yahoo.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: I request inclusion of SAS Transport Layer and AIC-94xx intothe kernel
Date: Fri, 30 Sep 2005 20:49:25 +0200 [thread overview]
Message-ID: <1128106165.3012.17.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <9BB4DECD4CFE6D43AA8EA8D768ED51C20F46D5@xbl3.ma.emulex.com>
On Fri, 2005-09-30 at 14:36 -0400, James.Smart@Emulex.Com wrote:
> > On Fri, 2005-09-30 at 13:07 -0400, Salyzyn, Mark wrote:
> > > At the SAS BOF, I indicated that it would not be much trouble to
> > > translate the CSMI handler in the aacraid driver to a similar sysfs
> > > arrangement. If such info can be mined from a firmware
> > based RAID card,
> > > every driver should be able to do so. The spec writers
> > really need to
> > > consider rewriting SDI for sysfs (if they have not already) and move
> > > away from an ABI.
> >
> > that makes me wonder... why and how does T10 control linux abi's ??
>
> Agreed. The most they should be doing is defining a library interface, and
> letting the library hide the system specifics (like t11 and hbaapi, who
> still got parts wrong). It also changes the argument from being a "linux abi"
> to being "a defacto application/library abi".
and not an ABI but an API. Which is important to allow the OS designers
deal with architecture differences better.
next prev parent reply other threads:[~2005-09-30 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 18:36 James.Smart
2005-09-30 18:49 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 22:25 James.Smart
2005-09-30 7:36 I request inclusion of SAS Transport Layer and AIC-94xx into the kernel Andre Hedrick
2005-09-30 18:34 ` Luben Tuikov
2005-09-30 18:50 ` Kyle Moffett
2005-09-30 19:08 ` Luben Tuikov
2005-09-30 21:31 ` Kyle Moffett
2005-09-30 22:14 ` Luben Tuikov
2005-10-01 0:33 ` Jeff Garzik
2005-10-03 14:18 ` Luben Tuikov
2005-10-03 14:26 ` I request inclusion of SAS Transport Layer and AIC-94xx intothe kernel David Lang
2005-10-03 15:19 ` Luben Tuikov
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=1128106165.3012.17.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=James.Smart@Emulex.Com \
--cc=Luben_Tuikov@adaptec.com \
--cc=andrew.patterson@hp.com \
--cc=dougg@torque.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ltuikov@yahoo.com \
--cc=mark_salyzyn@adaptec.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®