From: Martin Devera <devik@cdi.cz>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fusion-MPT slowness workaround
Date: Tue, 01 Nov 2005 19:11:52 +0100 [thread overview]
Message-ID: <4367AFE8.9080206@cdi.cz> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C04BE82D0@nacos172.co.lsil.com>
Moore, Eric Dean wrote:
> On Tuesday, November 01, 2005 10:46 AM, Martin Devera wrote:
>
>>because I ran into problem with fusion mpt scsi with 2.6.14 yesterday
>>I tried to find a workaround.
>>Because it seems that there is bug in DV code I patched driver to skip
>>DV and use firmware negotiation data.
>>It "works for me" both compiled-in and as module.
>>
>
>
> NACK. Disabling DV is not the solution.
>
> I have a fix I will post sometime this week.
excellent. Just to make it clear, I posted this one as quick workaround not
as final solution attempt.
Please consider CCing me when the patch will be available - I'll be pleased
to test it :-)
Martin
next prev parent reply other threads:[~2005-11-01 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 18:02 Fusion-MPT slowness workaround Moore, Eric Dean
2005-11-01 18:11 ` Martin Devera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-01 17:46 Martin Devera
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=4367AFE8.9080206@cdi.cz \
--to=devik@cdi.cz \
--cc=Eric.Moore@lsil.com \
--cc=linux-kernel@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