From: Christoph Hellwig <hch@infradead.org>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: Christoph Hellwig <hch@infradead.org>,
jeremy@sgi.com, linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] MPT Fusion driver 3.02.06 update
Date: Tue, 26 Oct 2004 18:15:25 +0100 [thread overview]
Message-ID: <20041026171525.GA15153@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57053AF0CB@exa-atlanta>
> > hooks it needs (e.g. the sas device list)
> >
>
> We have to ship with these IOCTLS. Are there any compromise?
> Sounds like you shot down my backup idea; e.g putting this code into
> seperate file which isn't provided for inclusion, but can be recompiled
> to link into mptctl? I don't think we time to pursue your the idea of
> re-invent everything into the sas-transport layer.
No way. This is similar to the hbaapi situation with qlogic and emulex.
If you had worked with us early on on an API like I told you multiple times
we'd have something sane now.
Btw, what part of HP badly wants this? I'm sure Grant and Matthew
could explain them internally what a bad idea this is.
>
> Jeremy Higdon asked me to add this, not SuSE.
Jeremy, can you make sure SuSE has an uptodate transport attribute
implementation ?
next prev parent reply other threads:[~2004-10-26 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 17:03 [ANNOUNCE] MPT Fusion driver 3.02.06 update Moore, Eric Dean
2004-10-26 17:15 ` Christoph Hellwig [this message]
2004-10-26 20:29 ` Jeremy Higdon
-- strict thread matches above, loose matches on Subject: below --
2004-10-26 17:20 James.Smart
2004-10-26 16:02 Moore, Eric Dean
2004-10-26 16:08 ` Christoph Hellwig
2004-10-25 23:32 Moore, Eric Dean
2004-10-26 8:09 ` Masao Fukuchi
2004-10-26 8:20 ` Douglas Gilbert
2004-10-26 9:53 ` Christoph Hellwig
2004-10-26 10:38 ` 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=20041026171525.GA15153@infradead.org \
--to=hch@infradead.org \
--cc=Emoore@lsil.com \
--cc=jeremy@sgi.com \
--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).