From: James Bottomley <jejb@steeleye.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Bruno Cornec <Bruno.Cornec@hp.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
tvignaud@mandrakesoft.com
Subject: Re: megaraid driver (proposed patch)
Date: Fri, 25 Mar 2005 13:04:37 -0600 [thread overview]
Message-ID: <1111777477.5692.29.camel@mulgrave> (raw)
In-Reply-To: <20050325184718.GA15215@infradead.org>
On Fri, 2005-03-25 at 18:47 +0000, Christoph Hellwig wrote:
> On Fri, Mar 25, 2005 at 12:39:52PM -0600, James Bottomley wrote:
> > On Fri, 2005-03-25 at 19:22 +0100, Bruno Cornec wrote:
> > > Would you consider to apply the following patch proposed by Thierry
> > > Vignaud as a solution for the MandrakeSoft kernel in the mainstream 2.6
> > > kernel ?
> >
> > Well, to be considered you'd need to cc the megaraid maintainers and the
> > linux-scsi mailing list.
> >
> > > -if MEGARAID_NEWGEN=n
> >
> > No, this is wrong it would break allyes configs and I'd get shot.
>
> Why? The megaraid drivers shouldn't have any conflicting non-static
> symbols
You get a kernel with two drivers trying to claim some of the same set
of cards. The winner will be the driver that gets its init routines
called first, but this isn't a desirable outcome.
I wouldn't object to a patch that allows both *modules* to be built,
which is all I think the distros are after.
James
next prev parent reply other threads:[~2005-03-25 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 18:22 megaraid driver (proposed patch) Bruno Cornec
2005-03-25 18:39 ` James Bottomley
2005-03-25 18:47 ` Christoph Hellwig
2005-03-25 19:04 ` James Bottomley [this message]
2005-03-25 19:07 ` Christoph Hellwig
2005-03-25 19:13 ` Ricardo Colon
2005-03-25 19:24 ` James Bottomley
2005-03-25 19:59 ` Bruno Cornec
2005-03-31 12:58 ` Thierry Vignaud
2005-03-31 13:01 ` 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=1111777477.5692.29.camel@mulgrave \
--to=jejb@steeleye.com \
--cc=Bruno.Cornec@hp.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tvignaud@mandrakesoft.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 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.