From: Christoph Hellwig <hch@infradead.org>
To: Duane Grigsby <duane.grigsby@qlogic.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Caushik, Ramesh" <ramesh.caushik@intel.com>,
device-mapper development <dm-devel@redhat.com>,
linux-raid@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org
Subject: Re: [dm-devel] [ANNOUNCE] multipath-tools-0.4.1
Date: Thu, 23 Dec 2004 19:17:54 +0000 [thread overview]
Message-ID: <20041223191754.GA30058@infradead.org> (raw)
In-Reply-To: <41EBA11203419D4CA8EB4C6140D8B401010212E4@AVEXCH01.qlogic.org>
On Thu, Dec 23, 2004 at 11:08:36AM -0800, Duane Grigsby wrote:
> The problem is we have to support the distros which do not have support for fc_transport, so I would suggest you use but the mainline driver as well.
I think that's those distributions problems. The FC and RHEL4 kernels
are pretty uptodate, and SLES9 has partial fc_transport support since
SP1. But they use the broken qlogic drivers instead of the mainline ones
anyway.
next prev parent reply other threads:[~2004-12-23 19:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 19:08 [dm-devel] [ANNOUNCE] multipath-tools-0.4.1 Duane Grigsby
2004-12-23 19:17 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 12:19 James.Smart
2004-12-22 21:54 Caushik, Ramesh
2004-12-23 13:28 ` Christoph Hellwig
2004-12-22 21:05 James.Smart
2004-12-22 23:30 ` christophe varoqui
2004-12-22 19:26 Caushik, Ramesh
2004-12-22 21:52 ` christophe varoqui
2004-12-21 22:02 Caushik, Ramesh
2004-12-22 1:09 ` christophe varoqui
2004-12-22 1:26 ` christophe varoqui
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=20041223191754.GA30058@infradead.org \
--to=hch@infradead.org \
--cc=dm-devel@redhat.com \
--cc=duane.grigsby@qlogic.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ramesh.caushik@intel.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).