From: "'Christoph Hellwig'" <hch@infradead.org>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: "'Arjan van de Ven'" <arjanv@redhat.com>,
"'James Bottomley'" <James.Bottomley@SteelEye.com>,
"'matt_domsch@dell.com'" <matt_domsch@dell.com>,
"'Paul Wagland'" <paul@wagland.net>,
Matthew Wilcox <willy@debian.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-al pha1
Date: Wed, 25 Feb 2004 20:44:41 +0000 [thread overview]
Message-ID: <20040225204441.A9291@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC3E7@exa-atlanta.se.lsil.com>; from Atulm@lsil.com on Wed, Feb 25, 2004 at 03:38:48PM -0500
On Wed, Feb 25, 2004 at 03:38:48PM -0500, Mukker, Atul wrote:
> > of their own, e.g. mptraid
> Although, this simplifies the development and maintenance effort, having a
> single driver to drive both controllers or two independent drivers is not
> always our decision. Most often, it would be Dell's preference.
Well, I think the people at Dell should get down from their fucking crackpipe
then. (Matt, did you hear that? please stop this kind of marketing driven
junk, thanks)
next prev parent reply other threads:[~2004-02-25 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 20:38 [SUBJECT CHANGE]: megaraid unified driver version 2.20.0.0-al pha1 Mukker, Atul
2004-02-25 20:44 ` 'Christoph Hellwig' [this message]
2004-02-25 21:38 ` Matt Domsch
2004-02-26 2:27 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 20:41 Mukker, Atul
2004-02-25 23:05 Mukker, Atul
2004-02-26 2:38 ` Jeff Garzik
2004-02-26 2:44 ` Matt Domsch
2004-02-26 7:43 ` Arjan van de Ven
2004-02-26 7:49 ` Jeff Garzik
2004-02-26 15:21 Mukker, Atul
2004-03-19 22:17 Mukker, Atul
2004-03-19 22:26 ` Matthew Wilcox
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=20040225204441.A9291@infradead.org \
--to=hch@infradead.org \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matt_domsch@dell.com \
--cc=paul@wagland.net \
--cc=willy@debian.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