From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Brian King <brking@linux.vnet.ibm.com>,
John Garry <john.garry@huawei.com>,
Brian King <brking@us.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Do we still need the scsi IPR driver ?
Date: Thu, 6 Oct 2022 06:21:35 +0900 [thread overview]
Message-ID: <9100d34c-26ab-fa19-15c6-cf626383cab1@opensource.wdc.com> (raw)
In-Reply-To: <5f2efa8a-8207-403c-12e8-74f43d8d8a14@linux.vnet.ibm.com>
On 10/6/22 02:20, Brian King wrote:
> On 9/20/22 8:07 AM, John Garry wrote:
>> On 21/06/2022 23:12, Damien Le Moal wrote:
>>>>> We still need it around for now. IBM still sells these adapters
>>>>> and they can still be ordered even on our latest Power 10 systems.
>>>> At one point I did look into modifying ipr to use an ->error_handler.
>>>> I recall I ran into some issues that resulted in this getting put
>>>> on the shelf, but its been a while. I'll go dig that code up and
>>>> see what it looks like.
>>> Thanks. It would be really great if you can convert to using
>>> error_handler. This is really the last ata/libsas driver that does not use
>>> this.
>>>
>>
>> Hi Brian,
>>
>> I am wondering if there is any update here?
>>
>> As you may have seen in [0], I think that we need to make progress on this topic first to keep the solution there a bit simpler.
>>
>> [0] https://lore.kernel.org/linux-scsi/1663669630-21333-1-git-send-email-john.garry@huawei.com/T/#mf890cb4f1627112652831524dca62cbde4a0a637
>
> I've made some progress. I was able to dig up the code to move ipr to use error_handler
> and have gotten it to compile, but haven't gotten to trying it in the lab yet.
Great ! Thanks for doing that.
>
> -Brian
>
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-10-05 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 4:48 Do we still need the scsi IPR driver ? Damien Le Moal
2022-06-20 7:35 ` Hannes Reinecke
2022-06-21 20:36 ` Brian King
2022-06-21 20:52 ` Brian King
2022-06-21 22:12 ` Damien Le Moal
2022-09-20 13:07 ` John Garry
2022-10-05 17:20 ` Brian King
2022-10-05 21:21 ` Damien Le Moal [this message]
2022-10-06 7:35 ` Hannes Reinecke
2022-10-13 3:36 ` Brian King
2023-03-10 9:56 ` John Garry
2023-03-13 23:43 ` Brian King
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=9100d34c-26ab-fa19-15c6-cf626383cab1@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=brking@linux.vnet.ibm.com \
--cc=brking@us.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).