From: Robert Borkowski <rborkows@novator.com>
To: jgarzik@pobox.com
Cc: linux-ide@vger.kernel.org
Subject: [PATCH] updated sata_promise.c with new device id
Date: Mon, 06 Feb 2006 14:17:08 -0500 [thread overview]
Message-ID: <43E7A0B4.4050908@novator.com> (raw)
patch is against kernel 2.4.32
card is a Promise SATAII 300 TX4, PDC40718-GP printed on the main chip
Tested by making md raid5 on four drives and stressing with bonnie++.
Any other tests I should run?
Signed-off-by: Robert Borkowski <rborkows@novator.com>
--- drivers/scsi/sata_promise.c.orig Mon Feb 6 11:45:06 2006
+++ drivers/scsi/sata_promise.c Mon Feb 6 11:45:39 2006
@@ -181,6 +181,8 @@
board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3319, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_20319 },
+ { PCI_VENDOR_ID_PROMISE, 0x3d17, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3d18, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
board_20319 },
--
Robert Borkowski
next reply other threads:[~2006-02-06 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 19:17 Robert Borkowski [this message]
2006-03-04 2:27 ` [PATCH] updated sata_promise.c with new device id Jeff Garzik
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=43E7A0B4.4050908@novator.com \
--to=rborkows@novator.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).