From: Christoph Hellwig <hch@lst.de>
To: John Garry <john.garry@huawei.com>
Cc: Christoph Hellwig <hch@lst.de>,
martin.petersen@oracle.com, brking@us.ibm.com,
jinpu.wang@cloud.ionos.com, mpe@ellerman.id.au,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: fix ATAPI support for libsas drivers
Date: Thu, 18 Jun 2020 17:28:48 +0200 [thread overview]
Message-ID: <20200618152848.GA30919@lst.de> (raw)
In-Reply-To: <d3459f71-501e-3fea-d5dc-a5599758459d@huawei.com>
On Thu, Jun 18, 2020 at 10:02:58AM +0100, John Garry wrote:
> On 15/06/2020 07:46, Christoph Hellwig wrote:
>> Hi all,
>>
>> this series fixes the ATAPI DMA drain refactoring for SAS HBAs that
>> use libsas.
>> .
>>
>
> Something I meant to ask before and was curious about, specifically since
> ipr doesn't actually use libsas: Why not wire up other SAS HBAs, like
> megaraid_sas?
megaraid_sas and mpt3sas don't use the libata code at all. ipr actually
is a special case and uses libata directly instead of libsas (something
I hadn't realized, but which doesn't change anything for the patches
itself, just possibly the commit log).
next prev parent reply other threads:[~2020-06-18 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 6:46 fix ATAPI support for libsas drivers Christoph Hellwig
2020-06-15 6:46 ` [PATCH 1/2] libata: provide a ata_scsi_dma_need_drain stub for !CONFIG_ATA Christoph Hellwig
2020-06-16 3:46 ` Martin K. Petersen
2020-06-15 6:46 ` [PATCH 2/2] scsi: wire up ata_scsi_dma_need_drain for SAS HBA drivers Christoph Hellwig
2020-06-16 0:39 ` kernel test robot
2020-06-18 9:02 ` fix ATAPI support for libsas drivers John Garry
2020-06-18 15:28 ` Christoph Hellwig [this message]
2020-06-22 6:28 ` Hannes Reinecke
2020-06-23 11:44 ` John Garry
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=20200618152848.GA30919@lst.de \
--to=hch@lst.de \
--cc=brking@us.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=john.garry@huawei.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.