From: Christoph Hellwig <hch@lst.de>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: jejb@steeleye.com, Linux SCSI List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] mark qlogicfc broken
Date: Fri, 11 Feb 2005 15:10:15 +0100 [thread overview]
Message-ID: <20050211141015.GA28665@lst.de> (raw)
In-Reply-To: <Pine.GSO.4.33.0502110847280.5536-100000@sweetums.bluetronic.net>
On Fri, Feb 11, 2005 at 09:06:14AM -0500, Ricky Beam wrote:
> On Thu, 10 Feb 2005, Christoph Hellwig wrote:
> >The hardware is supported by qla2xxx which is much better (and
> >maintained) driver. Keeping the driver around confuses people to
> >actually use it with severe results, e.g.
>
> That's a nice theory, but not so true in practice. qla2xxx will not
> correctly drive a 2100. I've complained about this for several years
> now and it still doesn't work. QLogic doesn't test the 2100 anymore.
> (Maybe not the 2200's either.)
Arjan tested it on the 2100 a while ago and it worked just fine. Have
you tested it recently?
> qlogicfc was removed from the tree once before only to be put back
> about 30sec later because people still use it. It's certainly not
> BROKEN. Not recommended, but not broken either. BROKEN is a tag for
> things that are _broken_ -- they don't compile and don't work when they
> do. qlogicfc both compiles and works, so BROKEN is the wrong thing to
> use.
It _is_ broken. See the url in my initial post.
next prev parent reply other threads:[~2005-02-11 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 18:18 [PATCH] mark qlogicfc broken Christoph Hellwig
2005-02-11 14:06 ` Ricky Beam
2005-02-11 14:10 ` Christoph Hellwig [this message]
2005-02-11 14:29 ` Ricky Beam
-- strict thread matches above, loose matches on Subject: below --
2005-02-11 18:08 Duane Grigsby
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=20050211141015.GA28665@lst.de \
--to=hch@lst.de \
--cc=jejb@steeleye.com \
--cc=jfbeam@bluetronic.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.