From: Paul Wagland <paul@kungfoocoder.org>
To: Linux SCSI mailing list <linux-scsi@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: akpm@osdl.org, torvalds@osdl.org,
James.Bottomley@HansenPartnership.com, atulm@lsil.com
Subject: [PATCH][BUGFIX] : Megaraid patch for 2.6 1/5
Date: Fri, 20 Feb 2004 03:05:39 +0100 [thread overview]
Message-ID: <1077242738.12567.76.camel@morsel.kungfoocoder.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hi all,
On Linux-SCSI over the last few days I have been discussing a couple of
problems with the 2.6.2 megaraid driver. This patch, originally
submitted by Christoph Hellwig, fixes the problem where the megaraid
driver could be removed, even though it was in use.
patch is attached and below.
diff --recursive --ignore-all-space --unified linux-2.6.2.o/drivers/scsi/megaraid.c linux-2.6.2.megaraid/drivers/scsi/megaraid.c
--- linux-2.6.2.o/drivers/scsi/megaraid.c 2004-02-09 22:56:09.000000000 +0100
+++ linux-2.6.2.megaraid/drivers/scsi/megaraid.c 2004-02-20 01:32:21.000000000 +0100
@@ -4614,6 +4614,7 @@
}
static struct scsi_host_template megaraid_template = {
+ .module = THIS_MODULE,
.name = "MegaRAID",
.proc_name = "megaraid",
.info = megaraid_info,
[-- Attachment #2: 1-megaraid.mod_owner.patch --]
[-- Type: text/x-patch, Size: 485 bytes --]
diff --recursive --ignore-all-space --unified linux-2.6.2.o/drivers/scsi/megaraid.c linux-2.6.2.megaraid/drivers/scsi/megaraid.c
--- linux-2.6.2.o/drivers/scsi/megaraid.c 2004-02-09 22:56:09.000000000 +0100
+++ linux-2.6.2.megaraid/drivers/scsi/megaraid.c 2004-02-20 01:32:21.000000000 +0100
@@ -4614,6 +4614,7 @@
}
static struct scsi_host_template megaraid_template = {
+ .module = THIS_MODULE,
.name = "MegaRAID",
.proc_name = "megaraid",
.info = megaraid_info,
next reply other threads:[~2004-02-20 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 2:05 Paul Wagland [this message]
2004-02-20 5:10 ` [PATCH][BUGFIX] : Megaraid patch for 2.6 1/5 Jeff Garzik
2004-02-20 8:55 ` 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=1077242738.12567.76.camel@morsel.kungfoocoder.org \
--to=paul@kungfoocoder.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@osdl.org \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=torvalds@osdl.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