From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: chenxiang <chenxiang66@hisilicon.com>
Cc: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<linuxarm@huawei.com>, <linux-scsi@vger.kernel.org>
Subject: Re: [RESEND PATCH 0/5] scsi: hisi_sas: Minor fixes and cleanups
Date: Wed, 13 Dec 2023 23:25:32 -0500 [thread overview]
Message-ID: <yq1o7etfm19.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1702525516-51258-1-git-send-email-chenxiang66@hisilicon.com> (chenxiang's message of "Thu, 14 Dec 2023 11:45:11 +0800")
> This series contain some fixes and cleanups including:
> - Set .phy_attached before notifying phyup event HISI_PHYEE_PHY_UP_PM;
> - Use standard error code instead of hardcode;
> - Check before using pointer variable;
> - Rollback some operations if FLR failed;
> - Correct the number of global debugfs registers;
Applied to 6.8/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2023-12-14 4:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 3:45 [RESEND PATCH 0/5] scsi: hisi_sas: Minor fixes and cleanups chenxiang
2023-12-14 3:45 ` [RESEND PATCH 1/5] scsi: hisi_sas: Set .phy_attached before notifing phyup event HISI_PHYE_PHY_UP_PM chenxiang
2023-12-14 3:45 ` [RESEND PATCH 2/5] scsi: hisi_sas: Replace with standard error code return value chenxiang
2023-12-14 3:45 ` [RESEND PATCH 3/5] scsi: hisi_sas: Check before using pointer variables chenxiang
2023-12-14 3:45 ` [RESEND PATCH 4/5] scsi: hisi_sas: Rollback some operations if FLR failed chenxiang
2023-12-14 3:45 ` [RESEND PATCH 5/5] scsi: hisi_sas: Correct the number of global debugfs registers chenxiang
2023-12-14 4:25 ` Martin K. Petersen [this message]
2023-12-19 2:18 ` [RESEND PATCH 0/5] scsi: hisi_sas: Minor fixes and cleanups 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=yq1o7etfm19.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=chenxiang66@hisilicon.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@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