From: John Garry <john.garry@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<jinpu.wang@cloud.ionos.com>
Cc: <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 0/4] scsi: libsas and users: Factor out internal abort code
Date: Thu, 3 Mar 2022 17:05:11 +0000 [thread overview]
Message-ID: <75437004-3dac-0c53-b72b-892396f8f0ca@huawei.com> (raw)
In-Reply-To: <eb107f83-373f-c489-502d-a1655271c06b@opensource.wdc.com>
On 03/03/2022 16:29, Damien Le Moal wrote:
> Traveling this week so testing will be difficult. I will try this first thing
> Monday next week.
>
>> This is based on mkp-scsi 5.18 staging queue @ commit f2ddbbea7780
Much appreciated!
Thanks,
john
next prev parent reply other threads:[~2022-03-03 17:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 12:18 John Garry
2022-03-03 12:18 ` [PATCH 1/4] scsi: libsas: Add sas_execute_internal_abort_single() John Garry
2022-03-03 16:31 ` Damien Le Moal
2022-03-04 9:33 ` John Garry
2022-04-20 12:21 ` Hannes Reinecke
2022-04-25 8:27 ` John Garry
2022-04-25 8:34 ` Hannes Reinecke
2022-04-25 8:51 ` John Garry
2022-03-03 12:18 ` [PATCH 2/4] scsi: libsas: Add sas_execute_internal_abort_dev() John Garry
2022-04-20 12:22 ` Hannes Reinecke
2022-03-03 12:18 ` [PATCH 3/4] scsi: pm8001: Use libsas internal abort support John Garry
2022-03-03 16:36 ` Damien Le Moal
2022-03-04 9:41 ` John Garry
2022-03-07 2:47 ` Damien Le Moal
2022-04-20 12:24 ` Hannes Reinecke
2022-03-03 12:18 ` [PATCH 4/4] scsi: hisi_sas: " John Garry
2022-03-03 16:42 ` Damien Le Moal
2022-03-04 9:47 ` John Garry
2022-04-20 12:29 ` Hannes Reinecke
2022-04-25 8:43 ` John Garry
2022-03-03 16:29 ` [PATCH 0/4] scsi: libsas and users: Factor out internal abort code Damien Le Moal
2022-03-03 17:05 ` John Garry [this message]
2022-03-07 0:55 ` Damien Le Moal
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=75437004-3dac-0c53-b72b-892396f8f0ca@huawei.com \
--to=john.garry@huawei.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=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
all inboxes | Powered by JetHome®