From: Arjan van de Ven <arjanv@redhat.com>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: "'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: [PATCH][BUGFIX] : megaraid patch for 2.10.1 (irq disable bug fix)
Date: Tue, 24 Feb 2004 22:14:20 +0100 [thread overview]
Message-ID: <20040224211420.GG26919@devserv.devel.redhat.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57033BC3DE@exa-atlanta.se.lsil.com>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Tue, Feb 24, 2004 at 04:02:34PM -0500, Mukker, Atul wrote:
> > > controllers and also a single code base, with a very small
> > footprint patch -
> > > if at all required, to support various kernels.
> >
> > I didn't say "no". I'm just warning you that you've chosen a
> > hard road
> > to hoe, particularly with the limited life of 2.4.
>
> In my opinion, maintaining support for 2.4 drivers and adding new
> controllers to it would be crucial for a considerable time to come even
there is a difference between just adding a pci id and adding all new
features.
> Do we want to discover controllers and devices directed solely by kernel and
> should driver interfere a little bit.
I always considered the megaraid code here extremely hairy... I'd love to
see it go when we can
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-24 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 21:02 [PATCH][BUGFIX] : megaraid patch for 2.10.1 (irq disable bug fix) Mukker, Atul
2004-02-24 21:14 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 16:04 Mukker, Atul
2004-02-24 16:47 ` James Bottomley
2004-02-24 20:43 ` Christoph Hellwig
2004-02-24 14:47 Mukker, Atul
2004-02-24 14:58 ` Matthew Wilcox
2004-02-24 15:06 ` James Bottomley
2004-02-24 20:33 ` Matt Domsch
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=20040224211420.GG26919@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@SteelEye.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