From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Elektrokinesis DJ <cpubuilder2@gmail.com>,
brking@linux.vnet.ibm.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: jejb@linux.ibm.com, john.g.garry@oracle.com,
linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
wenxiong@linux.ibm.com, Niklas Cassel <cassel@kernel.org>
Subject: Re: [PATCH] ipr: Remove SATA support
Date: Thu, 29 Feb 2024 14:04:56 -0800 [thread overview]
Message-ID: <18490fc9-7fda-41ee-803a-bda874c2b42d@opensource.wdc.com> (raw)
In-Reply-To: <CABa-fKRfE8B2TLVJASB9xQaOXDiYH3YCw0YEEg1UcGu2Le8xWw@mail.gmail.com>
On 2024/02/29 9:31, Elektrokinesis DJ wrote:
> I am dissatisfied with the decision to remove SATA from the ipr driver, I
> have multiple machines in my homelab that now require manual patching every
> time I would like to update the kernel and initrd image. Bladecenter PS700
> uses the ipr SCSI driver if you install a common SATA SSD into the Planar
> SAS slots. This limits me from being able to use newer kernels without
> patching, unless I would like to procure expensive SAS SSDs.
The ipr driver was the only libsas/ATA driver that had not been converted to the
new libata error handling, and was thus preventing necessary cleanups in libata.
When it was removed, it seemed that no-one was using ATA devices with IPR beside
SATA DVDs, and very few people had this hardware to test anything.
So it seems that devices beside DVDs were/are actually used.
We can try to reintroduce the support for ATA in ipr, but that will not be a
simple revert as the new EH handling needs to be supported.
Brian,
Any comment ? Is this feasible ?
I do not have the hardware to work on this, so patches will have to be done by
you or someone with access.
--
Damien Le Moal
Western Digital Research
parent reply other threads:[~2024-02-29 22:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CABa-fKRfE8B2TLVJASB9xQaOXDiYH3YCw0YEEg1UcGu2Le8xWw@mail.gmail.com>]
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=18490fc9-7fda-41ee-803a-bda874c2b42d@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=brking@linux.vnet.ibm.com \
--cc=cassel@kernel.org \
--cc=cpubuilder2@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=john.g.garry@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=wenxiong@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).