From: Christoph Hellwig <hch@lst.de>
To: Mark_Salyzyn@adaptec.com, markus.lidel@shadowconnect.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: what to do with dpt_i2o
Date: Sat, 9 Oct 2004 17:01:14 +0200 [thread overview]
Message-ID: <20041009150114.GA21229@lst.de> (raw)
In-Reply-To: <20040925134622.GA19871@lst.de>
On Sat, Sep 25, 2004 at 03:46:22PM +0200, Christoph Hellwig wrote:
> Marcus, you'd been doing a lot of testing with the DPT/Adaptec cards for
> the new i2o layer, right? IIRC we now have both support for the Adaptec
> managment utils and the optimizes sglist format, so there's probably no
> reason anymore to keep dpt_i2o.
>
> If OTOH we want to keep it it would be nice of Mark could finally send
> the last round of patches we had agreed on..
ping..
next prev parent reply other threads:[~2004-10-09 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 13:46 what to do with dpt_i2o Christoph Hellwig
2004-10-09 15:01 ` Christoph Hellwig [this message]
2004-10-11 8:30 ` Markus Lidel
-- strict thread matches above, loose matches on Subject: below --
2004-10-11 12:28 Salyzyn, Mark
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=20041009150114.GA21229@lst.de \
--to=hch@lst.de \
--cc=Mark_Salyzyn@adaptec.com \
--cc=linux-scsi@vger.kernel.org \
--cc=markus.lidel@shadowconnect.com \
/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).