From: Jinpu Wang <jinpu.wang@ionos.com>
To: John Garry <john.garry@huawei.com>
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
jinpu.wang@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 07:23:19 +0100 [thread overview]
Message-ID: <CAMGffE=jBKnPa4egHBUApHo2=SpyRyZk98eS-rX8SbN_VCNdPw@mail.gmail.com> (raw)
In-Reply-To: <1647001432-239276-1-git-send-email-john.garry@huawei.com>
On Fri, Mar 11, 2022 at 1:29 PM John Garry <john.garry@huawei.com> wrote:
>
> 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.
>
> Again, testing and review would be appreciated.
>
> This is based on mkp-scsi 5.18 staging queue @ commit 2bd3b6b75946
>
> Changes since v1:
> - fixup small coding issues (Damien)
> - Add Tested-by tags (thanks!)
>
> John Garry (4):
> scsi: libsas: Add sas_execute_internal_abort_single()
> scsi: libsas: Add sas_execute_internal_abort_dev()
> scsi: pm8001: Use libsas internal abort support
> scsi: hisi_sas: Use libsas internal abort support
Looks good to me!
Acked-by: Jack Wang <jinpu.wang@ionos.com>
Thanks John for doing it!
>
> drivers/scsi/hisi_sas/hisi_sas.h | 8 +-
> drivers/scsi/hisi_sas/hisi_sas_main.c | 453 +++++++++----------------
> drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 11 +-
> drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 18 +-
> drivers/scsi/libsas/sas_scsi_host.c | 89 +++++
> drivers/scsi/pm8001/pm8001_hwi.c | 27 +-
> drivers/scsi/pm8001/pm8001_hwi.h | 5 -
> drivers/scsi/pm8001/pm8001_sas.c | 178 +++-------
> drivers/scsi/pm8001/pm8001_sas.h | 6 +-
> drivers/scsi/pm8001/pm80xx_hwi.h | 5 -
> include/scsi/libsas.h | 24 ++
> include/scsi/sas.h | 2 +
> 12 files changed, 360 insertions(+), 466 deletions(-)
>
> --
> 2.26.2
>
next prev parent reply other threads:[~2022-03-14 6:23 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 ` Jinpu Wang [this message]
2022-03-15 3:33 ` [PATCH v2 0/4] scsi: libsas and users: Factor out internal abort code Martin K. Petersen
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='CAMGffE=jBKnPa4egHBUApHo2=SpyRyZk98eS-rX8SbN_VCNdPw@mail.gmail.com' \
--to=jinpu.wang@ionos.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=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liuqi115@huawei.com \
--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).