From: John Garry <john.garry@huawei.com>
To: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>
Cc: <yanaijie@huawei.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
John Garry <john.garry@huawei.com>
Subject: [PATCH 0/4] hisi_sas: Some misc patches for next
Date: Tue, 12 Oct 2021 20:26:24 +0800 [thread overview]
Message-ID: <1634041588-74824-1-git-send-email-john.garry@huawei.com> (raw)
This small series includes the following:
- Relocate the init device functionality to a more appropriate location
- Make the phy control function synchronous
- For faulty SATA disk, disable their phy to stop spinning in the error
handler
- For previous patch we need to export a libsas phy control function
Thanks!
Luo Jiaxing (2):
scsi: libsas: Export sas_phy_enable()
scsi: hisi_sas: Disable SATA disk phy for severe I_T nexus reset
failure
Xiang Chen (2):
scsi: hisi_sas: Initialise devices in .slave_alloc callback
scsi: hisi_sas: Wait for phyup in hisi_sas_control_phy()
drivers/scsi/hisi_sas/hisi_sas.h | 1 +
drivers/scsi/hisi_sas/hisi_sas_main.c | 89 ++++++++++++++++++++------
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 13 +---
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 19 ++----
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 11 +---
drivers/scsi/libsas/sas_init.c | 3 +-
include/scsi/libsas.h | 1 +
7 files changed, 84 insertions(+), 53 deletions(-)
--
2.26.2
next reply other threads:[~2021-10-12 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 12:26 John Garry [this message]
2021-10-12 12:26 ` [PATCH 1/4] scsi: hisi_sas: Initialise devices in .slave_alloc callback John Garry
2021-10-12 12:26 ` [PATCH 2/4] scsi: hisi_sas: Wait for phyup in hisi_sas_control_phy() John Garry
2021-10-12 12:26 ` [PATCH 3/4] scsi: libsas: Export sas_phy_enable() John Garry
2021-10-12 12:26 ` [PATCH 4/4] scsi: hisi_sas: Disable SATA disk phy for severe I_T nexus reset failure John Garry
2021-10-13 2:46 ` [PATCH 0/4] hisi_sas: Some misc patches for next Martin K. Petersen
2021-10-21 3:42 ` 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=1634041588-74824-1-git-send-email-john.garry@huawei.com \
--to=john.garry@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=yanaijie@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