From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: jejb@linux.vnet.ibm.com, John Garry <john.garry@huawei.com>
Cc: "Martin K . Petersen" <martin.petersen@oracle.com>,
linuxarm@huawei.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] hisi_sas: Some misc patches
Date: Tue, 19 May 2020 22:30:06 -0400 [thread overview]
Message-ID: <158994171817.20861.14065822562297716117.b4-ty@oracle.com> (raw)
In-Reply-To: <1589552025-165012-1-git-send-email-john.garry@huawei.com>
On Fri, 15 May 2020 22:13:41 +0800, John Garry wrote:
> This series includes some misc patches, generally tidy-up. The most
> significant is the patch to not reset the phy up timer for when the
> phy is already up - the HW designers do not have an answer for why this
> occurs, so we workaround.
>
> John Garry (1):
> scsi: hisi_sas: Stop returning error code from slot_complete_vX_hw()
>
> [...]
Applied to 5.8/scsi-queue, thanks!
[1/4] scsi: hisi_sas: Do not reset phy timer to wait for stray phy up
https://git.kernel.org/mkp/scsi/c/e16b9ed61e07
[2/4] scsi: hisi_sas: Modify the commit information for DSM method
https://git.kernel.org/mkp/scsi/c/1e954d1f002d
[3/4] scsi: hisi_sas: Add SAS_RAS_INTR0 to debugfs register name list
https://git.kernel.org/mkp/scsi/c/1a0efb55b2bb
[4/4] scsi: hisi_sas: Stop returning error code from slot_complete_vX_hw()
https://git.kernel.org/mkp/scsi/c/1cdee0044261
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2020-05-20 2:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 14:13 John Garry
2020-05-15 14:13 ` [PATCH 1/4] scsi: hisi_sas: Do not reset phy timer to wait for stray phyup John Garry
2020-05-15 14:13 ` [PATCH 2/4] scsi: hisi_sas: Modify the commit information for DSM method John Garry
2020-05-15 14:13 ` [PATCH 3/4] scsi: hisi_sas: Add SAS_RAS_INTR0 to debugfs register name list John Garry
2020-05-15 14:13 ` [PATCH 4/4] scsi: hisi_sas: Stop returning error code from slot_complete_vX_hw() John Garry
2020-05-20 2:30 ` Martin K. Petersen [this message]
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=158994171817.20861.14065822562297716117.b4-ty@oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®