[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <106f384f-d9e2-905d-5ac5-fe4ffd962122@virtuozzo.com>
Date: Wed, 19 Oct 2022 20:00:50 +0200
From: Konstantin Khorenko <khorenko@...tuozzo.com>
To: James Hilliard <james.hilliard1@...il.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Christian Großegger <christian@...ssegger.com>,
linux-scsi@...r.kernel.org,
Adaptec OEM Raid Solutions <aacraid@...rosemi.com>,
Sagar Biradar <sagar.biradar@...rochip.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Don Brace <don.brace@...rochip.com>
Subject: Re: [PATCH v3 0/1] aacraid: Host adapter Adaptec 6405 constantly
resets under high io load
On 10.10.2022 14:31, James Hilliard wrote:
> On Tue, Feb 22, 2022 at 10:41 PM Martin K. Petersen
> <martin.petersen@...cle.com> wrote:
>>
>>
>> Christian,
>>
>>> The faulty patch (Commit: 395e5df79a9588abf) from 2017 should be
>>> repaired with Konstantin Khorenko (1):
>>>
>>> scsi: aacraid: resurrect correct arc ctrl checks for Series-6
>>
>> It would be great to get this patch resubmitted by Konstantin and acked
>> by Microchip.
>
> Does the patch need to be rebased?
James, i have just checked - the old patch (v3) applies cleanly onto latest master branch.
> Based on this it looks like someone at microchip may have already reviewed:
> v3 changes:
> * introduced another wrapper to check for devices except for Series 6
> controllers upon request from Sagar Biradar (Microchip)
Well, back in the year 2019 i've created a bug in RedHat bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1724077
(the bug is private, this is default for Redhat bugs)
In this bug Sagar Biradar (with the email @microchip.com) suggested me to rework the patch - i've done
that and sent the v3.
And nothing happened after that, but in a ~year (2020-06-19) the bug was closed with the resolution
NOTABUG and a comment that S6 users will find the patch useful.
i suppose S6 is so old that RedHat just does not have customers using it and Microchip company itself
is also not that interested in handling so old hardware issues.
Sorry, i was unable to get a final ack from Microchip,
i've written direct emails to the addresses which is found in the internet, tried to connect via
linkedin, no luck.
--
Konstantin Khorenko
Powered by blists - more mailing lists