[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <237c4979-c7ab-22d9-35ca-dda1afab2d11@gmail.com>
Date: Wed, 19 Jun 2019 13:47:23 +1200
From: Michael Schmitz <schmitzmic@...il.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Finn Thain <fthain@...egraphics.com.au>,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v2 2/7] scsi: NCR5380: Always re-enable reselection
interrupt
Martin,
On 19/06/19 12:47 PM, Martin K. Petersen wrote:
> Michael,
>
>> No matter - patch applied cleanly to what I'm running on my Falcon,
>> and works just fine for now (stresstest will take a few hours to
>> complete). And that'll thoroughly exercise the reselection code path,
>> from what we've seen before.
> How did it go?
Just fine - repeated with different settings for can_queue and
cmd_per_lun, with not a single hitch. No regression at all.
Cheers,
Michael
>
Powered by blists - more mailing lists