linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
	sreenib@lsil.com, sju@lsil.com
Subject: [PATCH] Allow both megaraid drivers to be built
Date: Mon, 29 Aug 2005 18:30:23 +0100	[thread overview]
Message-ID: <4313462F.9030904@gentoo.org> (raw)
In-Reply-To: <20050829150209.GA5563@infradead.org>

Christoph Hellwig wrote:
> ifdef on other drivers is bogus, please remove the pci ids completely
> from the old driver.  It'd probably be a good idea to rename it to
> megaraid_legacy aswell.  I've also asked the LSI Engineers whether they
> could help identifying what code could be remove when only supporting
> the two oldes chips but haven't gotten a reply yet.  I hope they'll
> be able to answer when they're less busy.

Thanks for the feedback. Here's a new patch.



Rename megaraid to megaraid_legacy, changing the filenames, sysfs name, module 
name, and the messages printed out via printk. I have left the procfs name as 
"megaraid" as presumably userspace tools rely on this.

Remove hardware ID's from megaraid_legacy which overlap with the newgen 
megaraid drivers.

Allow megaraid_legacy to be built alongside the newgen driver.

Signed-off-by: Daniel Drake <dsd@gentoo.org>



As the patch is large (300K) I am not including it in this mail. You can get 
it here:

	http://dev.gentoo.org/~dsd/megaraid_legacy.patch

Thanks,
Daniel

      reply	other threads:[~2005-08-29 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29 14:50 [PATCH] Allow both megaraid drivers to be built Daniel Drake
2005-08-29 15:02 ` Christoph Hellwig
2005-08-29 17:30   ` Daniel Drake [this message]

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=4313462F.9030904@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sju@lsil.com \
    --cc=sreenib@lsil.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 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).