From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<jinpu.wang@cloud.ionos.com>, <damien.lemoal@opensource.wdc.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<Ajish.Koshy@microchip.com>, <linuxarm@huawei.com>,
<Viswas.G@microchip.com>, <hch@lst.de>, <liuqi115@huawei.com>,
<chenxiang66@hisilicon.com>
Subject: Re: [PATCH v2 0/4] scsi: libsas and users: Factor out internal abort code
Date: Mon, 14 Mar 2022 23:33:59 -0400 [thread overview]
Message-ID: <yq1y21bdh44.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1647001432-239276-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Fri, 11 Mar 2022 20:23:48 +0800")
John,
> This is a follow-on from the series to factor out the TMF code shared
> between libsas LLDDs.
>
> The hisi_sas and pm8001 have an internal abort feature to abort
> pending commands in the host controller, prior to being sent to the
> target. The driver support implementation is naturally quite similar,
> so factor it out.
Applied to 5.18/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-03-15 3:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:23 [PATCH v2 0/4] scsi: libsas and users: Factor out internal abort code John Garry
2022-03-11 12:23 ` [PATCH v2 1/4] scsi: libsas: Add sas_execute_internal_abort_single() John Garry
2022-03-11 12:23 ` [PATCH v2 2/4] scsi: libsas: Add sas_execute_internal_abort_dev() John Garry
2022-03-11 12:23 ` [PATCH v2 3/4] scsi: pm8001: Use libsas internal abort support John Garry
2022-03-11 12:23 ` [PATCH v2 4/4] scsi: hisi_sas: " John Garry
2022-03-14 6:23 ` [PATCH v2 0/4] scsi: libsas and users: Factor out internal abort code Jinpu Wang
2022-03-15 3:33 ` Martin K. Petersen [this message]
2022-03-19 3:56 ` Martin K. Petersen
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=yq1y21bdh44.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Ajish.Koshy@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=chenxiang66@hisilicon.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=jinpu.wang@cloud.ionos.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuqi115@huawei.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