From: Jeff Garzik <jgarzik@pobox.com>
To: Robert Borkowski <rborkows@novator.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] updated sata_promise.c with new device id
Date: Fri, 03 Mar 2006 21:27:06 -0500 [thread overview]
Message-ID: <4408FAFA.9090704@pobox.com> (raw)
In-Reply-To: <43E7A0B4.4050908@novator.com>
Robert Borkowski wrote:
> 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 },
>
Can you resend against 2.6.x?
Jeff
prev parent reply other threads:[~2006-03-04 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 19:17 [PATCH] updated sata_promise.c with new device id Robert Borkowski
2006-03-04 2:27 ` Jeff Garzik [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=4408FAFA.9090704@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rborkows@novator.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).