From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Prakash, Sathya" <Sathya.Prakash@lsi.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Moore, Eric" <Eric.Moore@lsi.com>
Subject: RE: Fix for problems introduced by enabling MSI by default for MPT SPI controllers
Date: Thu, 10 Jul 2008 08:56:27 -0500 [thread overview]
Message-ID: <1215698187.3353.13.camel@localhost.localdomain> (raw)
In-Reply-To: <6A4D764DC1BDE14495DA8DC60A3D69531E95D72405@hkgmail01.lsi.com>
On Thu, 2008-07-10 at 16:38 +0800, Prakash, Sathya wrote:
> We have some known cases of MSI not working with FC and SPI controllers, that is the reason we don't want to enable the MSI for them by default.
Is that because of motherboard problems or because of actual on board
issues with the fusion controller?
James
prev parent reply other threads:[~2008-07-10 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 6:54 Fix for problems introduced by enabling MSI by default for MPT SPI controllers Prakash, Sathya
2008-07-09 14:10 ` James Bottomley
2008-07-10 8:38 ` Prakash, Sathya
2008-07-10 13:56 ` James Bottomley [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=1215698187.3353.13.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--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