From: chenxiang <chenxiang66@hisilicon.com>
To: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linuxarm@huawei.com>,
Xiang Chen <chenxiang66@hisilicon.com>
Subject: [PATCH 0/4] scsi: hisi_sas: Some misc changes
Date: Mon, 20 Mar 2023 11:34:21 +0800 [thread overview]
Message-ID: <1679283265-115066-1-git-send-email-chenxiang66@hisilicon.com> (raw)
From: Xiang Chen <chenxiang66@hisilicon.com>
This series contain some fixes including:
- Grab sas_dev lock when traversing sas_dev list to avoid NULL pointer
- Handle NCQ error when IPTT is valid
- Ensure all enabled PHYs up during controller reset
- Exit suspend state when usage count of runtime PM is greater than 0
Xingui Yang (2):
scsi: hisi_sas: Grab sas_dev lock when traversing the members of
sas_dev.list
scsi: hisi_sas: Handle NCQ error when IPTT is valid
Yihang Li (2):
scsi: hisi_sas: Ensure all enabled PHYs up during controller reset
scsi: hisi_sas: Exit suspending state when usage count is greater than
0
drivers/scsi/hisi_sas/hisi_sas.h | 3 +-
drivers/scsi/hisi_sas/hisi_sas_main.c | 57 ++++++++++++++++++-----
drivers/scsi/hisi_sas/hisi_sas_v1_hw.c | 8 +++-
drivers/scsi/hisi_sas/hisi_sas_v2_hw.c | 8 +++-
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 83 ++++++++++++++++++++++++++--------
5 files changed, 124 insertions(+), 35 deletions(-)
--
2.8.1
next reply other threads:[~2023-03-20 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 3:34 chenxiang [this message]
2023-03-20 3:34 ` [PATCH 1/4] scsi: hisi_sas: Grab sas_dev lock when traversing the members of sas_dev.list chenxiang
2023-03-20 3:34 ` [PATCH 2/4] scsi: hisi_sas: Handle NCQ error when IPTT is valid chenxiang
2023-03-20 3:34 ` [PATCH 3/4] scsi: hisi_sas: Ensure all enabled PHYs up during controller reset chenxiang
2023-03-20 3:34 ` [PATCH 4/4] scsi: hisi_sas: Exit suspending state when usage count is greater than 0 chenxiang
2023-04-03 1:59 ` [PATCH 0/4] scsi: hisi_sas: Some misc changes Martin K. Petersen
2023-04-12 2:04 ` 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=1679283265-115066-1-git-send-email-chenxiang66@hisilicon.com \
--to=chenxiang66@hisilicon.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@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).