public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: "Mukker, Atul" <Atulm@lsil.com>,
	"'Paul Wagland'" <paul@wagland.net>,
	Matthew Wilcox <willy@debian.org>,
	"Bagalkote, Sreenivas" <sreenib@lsil.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH][BUGFIX] : megaraid patch for 2.10.1 (irq disable bug fix)
Date: Tue, 24 Feb 2004 14:33:58 -0600	[thread overview]
Message-ID: <20040224143358.A18783@lists.us.dell.com> (raw)
In-Reply-To: <1077635204.2152.16.camel@mulgrave>; from James.Bottomley@steeleye.com on Tue, Feb 24, 2004 at 09:06:43AM -0600

On Tue, Feb 24, 2004 at 09:06:43AM -0600, James Bottomley wrote:
> On Tue, 2004-02-24 at 08:47, Mukker, Atul wrote:
> > We are in process of releasing a unified driver, which will natively support
> > the 2.4.x and 2.6.x kernels. 
> 
> I really don't think this will be such a good idea since you don't
> currently have a unified driver.  2.4 is approaching end of life as far
> as major driver updates go and the 2.6 APIs are quite a bit different. 
> You'll find it's a lot of work for a driver that will carry you at most
> six months before the distributions all switch to 2.6 and you find the
> 2.4 compatibility layer to be more of a hindrance than a help.

Distributions with 2.4 kernels will continue to live on for quite a
while. Red Hat Enterprise Linux has a 5-year support life, during
which we would expect LSI to release new hardware, and we would want
to be able to have that hardware work on that OS somehow.  The driver
source for 2.4 and 2.6 need not be identical, but there *will* be
ongoing maintenance for drivers on 2.4 kernels for the next several
years.  We're <6 months into the RHEL3 supported lifetime.

While I understand the concerns with keeping 2.4 and 2.6 drivers
separate, we can't ignore the maintenance for 2.4 drivers.  If that's
done on a 2.4-only stream, or cleanly with a joint 2.4/2.6 driver, I
don't care, but agree it's difficult to do a clean joint driver,
especially with all the SCSI subsystem changes.

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-24 20:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 14:47 [PATCH][BUGFIX] : megaraid patch for 2.10.1 (irq disable bug fix) Mukker, Atul
2004-02-24 14:58 ` Matthew Wilcox
2004-02-24 15:06 ` James Bottomley
2004-02-24 20:33   ` Matt Domsch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-24 21:02 Mukker, Atul
2004-02-24 21:14 ` Arjan van de Ven
2004-02-24 16:04 Mukker, Atul
2004-02-24 16:47 ` James Bottomley
2004-02-24 20:43 ` Christoph Hellwig
2004-02-23 17:24 Bagalkote, Sreenivas
2004-02-23 17:29 ` Matthew Wilcox
2004-02-24  7:09   ` Paul Wagland

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=20040224143358.A18783@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=Atulm@lsil.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=paul@wagland.net \
    --cc=sreenib@lsil.com \
    --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