From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Bagalkote, Sreenivas" <Sreenivas.Bagalkote@engenio.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
Daniel Drake <dsd@gentoo.org>,
"Kolli, Neela Syam" <Neela.Kolli@engenio.com>,
linux-scsi@vger.kernel.org, "Ju,
Seokmann" <Seokmann.Ju@engenio.com>
Subject: RE: [PATCH resend] Allow both megaraid drivers to be built
Date: Mon, 07 Nov 2005 07:22:34 -0600 [thread overview]
Message-ID: <1131369754.3316.2.camel@mulgrave> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57060CD30D@exa-atlanta>
On Mon, 2005-11-07 at 01:41 -0500, Bagalkote, Sreenivas wrote:
> You mean, you want to allow both drivers to be built and loaded together,
> even though they have overlapping ids?!
You're not thinking like a distribution. They want to build one kernel
for almost every configuration. There are a few things (SMP, bigmem
etc) that they're willing to build extra kernels for, but not, I think,
for old vs new megaraid. Thus they have to patch this up to build the
two modules. By and large, the overlapping ID business is sorted out by
the installer, although having disjoint IDs is good since the installer
doesn't have to make a choice.
Can you get this sorted out before 2.6.15, please (so if I believe
Linus, that's about five weeks)?
Thanks,
James
next prev parent reply other threads:[~2005-11-07 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 6:41 [PATCH resend] Allow both megaraid drivers to be built Bagalkote, Sreenivas
2005-11-07 11:36 ` 'Christoph Hellwig'
2005-11-07 13:22 ` James Bottomley [this message]
2005-11-07 14:08 ` [PATCH] Schedule removal of megaraid hardware support overlap Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2005-11-07 14:09 [PATCH resend] Allow both megaraid drivers to be built Bagalkote, Sreenivas
2005-11-07 6:05 Bagalkote, Sreenivas
2005-11-07 6:15 ` Christoph Hellwig
2005-11-07 14:14 ` Daniel Drake
2005-10-29 13:24 Daniel Drake
2005-11-06 18:47 ` James Bottomley
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=1131369754.3316.2.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Neela.Kolli@engenio.com \
--cc=Seokmann.Ju@engenio.com \
--cc=Sreenivas.Bagalkote@engenio.com \
--cc=dsd@gentoo.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).