All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: 'Christoph Hellwig' <hch@infradead.org>,
	"Mukker, Atul" <Atulm@lsil.com>,
	'Arjan van de Ven' <arjanv@redhat.com>,
	'James Bottomley' <James.Bottomley@SteelEye.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 15:38:21 -0600	[thread overview]
Message-ID: <20040225153821.C14838@lists.us.dell.com> (raw)
In-Reply-To: <20040225204441.A9291@infradead.org>; from hch@infradead.org on Wed, Feb 25, 2004 at 08:44:41PM +0000

On Wed, Feb 25, 2004 at 08:44:41PM +0000, 'Christoph Hellwig' wrote:
> 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)

Yes, I'll try to figure out where this request came from, if from
anyone at Dell.  My guess is it's related to other operating systems,
over which I have no control, but isn't relevant to Linux.

In general, I tend to fight exactly the opposite - people wanting
drivers split out for "new technology" - say, PCI Express, when the
driver<->firmware API hasn't changed, which is just wrong again.

If it's got a different driver<->firmware API, then it needs a new
driver.  If it's the same API, then it should be the same driver.

FWIW, I'm out of the office for the next couple weeks with a new baby,
thus limited sleep and access to people, but I'll discover what I
can, and will take the heat internally for saying "split the driver"
if in fact you've got two different APIs, as I suspect you do.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

  reply	other threads:[~2004-02-25 21:39 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'
2004-02-25 21:38   ` Matt Domsch [this message]
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=20040225153821.C14838@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=Atulm@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=arjanv@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 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.