From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <djwong@us.ibm.com>,
Chris McDermott <lcm@us.ibm.com>,
Luvella McFadden <luvella@us.ibm.com>,
AJ Johnson <blujuice@us.ibm.com>,
Kevin Stansell <kstansel@us.ibm.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Mauelshagen@redhat.com
Subject: RE: [PATCH] aic79xx should be able to ignore HostRAID enabled adapters
Date: Fri, 02 Dec 2005 19:06:19 +0000 [thread overview]
Message-ID: <1133550379.3515.14.camel@localhost> (raw)
In-Reply-To: <547AF3BD0F3F0B4CBDC379BAC7E4189F01E3E318@otce2k03.adaptec.com>
On Iau, 2005-12-01 at 08:44 -0500, Salyzyn, Mark wrote:
> I have on numerous attempts tried to contact Heinz Mauelshagen to
> fortify dmraid in support of the HostRAID adapters. He has yet to
> respond to my emails to start a dialogue with Adaptec.
That suprises me. Heinz does respond to things and actively asks for
help on stuff like dmraid
> Justin Gibbs had provided the community the emd driver, soundly rejected
> and never ported to dm because there were features that Justin held dear
> in md that do not translate to dm. An unfortunate waste of considerable
> resources.
Please understand Justin Gibbs gave the Linux community emd in about as
productive a way that the US/UK government "gave" Iraq democracy.
Whatever the reasons for that and where the fault lies is another matter
but the result was not productive.
For long term maintenance and sanity reasons Linux is about doing things
in a logical consistent manner. Many people have had to learn to do
things the way Linus wants or the kernel expects, me included. It is
from that sort of process we have the current excellent e100 ethernet
driver still from Intel but not at all the Intel original for example.
We've consistently avoided hiding software raid behind magical
abstractions. There are numerous reasons for this. We want disks to move
between controllers easily for example, which vendors usually want to
make as painful as possible to create lockin.
next prev parent reply other threads:[~2005-12-06 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 13:44 [PATCH] aic79xx should be able to ignore HostRAID enabled adapters Salyzyn, Mark
2005-12-01 14:12 ` Arjan van de Ven
2005-12-01 14:47 ` Heinz Mauelshagen
2005-12-03 11:22 ` Matthias Andree
2005-12-03 16:19 ` Jeff Garzik
2005-12-03 16:39 ` Matthias Andree
2005-12-01 17:44 ` Christoph Hellwig
2005-12-01 17:56 ` Jeff Garzik
2005-12-01 17:49 ` Jeff Garzik
2005-12-02 19:06 ` Alan Cox [this message]
[not found] <5ePEj-2gB-9@gated-at.bofh.it>
[not found] ` <5eQqA-3pv-7@gated-at.bofh.it>
[not found] ` <5eRZp-5KA-7@gated-at.bofh.it>
2005-12-02 0:38 ` Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2005-12-01 18:46 Salyzyn, Mark
2005-12-01 19:19 ` Jeff Garzik
2005-12-05 21:06 ` Darrick J. Wong
2005-12-05 21:25 ` Jeff Garzik
2005-12-06 9:14 ` Heinz Mauelshagen
2005-12-01 5:57 Darrick J. Wong
2005-12-01 6:41 ` Jeff Garzik
2005-12-01 8:22 ` Darrick J. Wong
2005-12-01 8:08 ` Arjan van de Ven
2005-12-01 11:26 ` 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=1133550379.3515.14.camel@localhost \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Mauelshagen@redhat.com \
--cc=blujuice@us.ibm.com \
--cc=djwong@us.ibm.com \
--cc=hch@infradead.org \
--cc=kstansel@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luvella@us.ibm.com \
--cc=mark_salyzyn@adaptec.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