From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.orgc>,
<linuxarm@huawei.com>
Subject: Re: [PATCH 0/6] hisi_sas: Some misc patches
Date: Mon, 12 Apr 2021 23:12:29 -0400 [thread overview]
Message-ID: <yq1eefe98tl.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1617709711-195853-1-git-send-email-john.garry@huawei.com> (John Garry's message of "Tue, 6 Apr 2021 19:48:25 +0800")
John,
> This series contains some more minor patches for the driver, including:
> - Improve debugfs code to snapshot registers prior to reset
> - Fix probe error path
> - Remove unused code
> - Print SAS address in some error logs to assist debugging
Applied to 5.13/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2021-04-13 3:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 11:48 [PATCH 0/6] hisi_sas: Some misc patches John Garry
2021-04-06 11:48 ` [PATCH 1/6] scsi: hisi_sas: Delete some unused callbacks John Garry
2021-04-06 11:48 ` [PATCH 2/6] scsi: hisi_sas: Print SAS address for v3 hw erroneous completion print John Garry
2021-04-06 11:48 ` [PATCH 3/6] scsi: hisi_sas: Call sas_unregister_ha() to roll back if .hw_init() fails John Garry
2021-04-06 11:48 ` [PATCH 4/6] scsi: hisi_sas: Directly snapshot registers when executing a reset John Garry
2021-04-06 11:48 ` [PATCH 5/6] scsi: hisi_sas: Warn in v3 hw channel interrupt handler when status reg cleared John Garry
2021-04-06 11:48 ` [PATCH 6/6] scsi: hisi_sas: Print SATA device SAS address for soft reset failure John Garry
2021-04-13 3:12 ` Martin K. Petersen [this message]
2021-04-16 2:51 ` [PATCH 0/6] hisi_sas: Some misc patches Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2019-05-29 9:58 John Garry
2019-05-29 9:58 ` John Garry
2019-06-05 2:21 ` Martin K. Petersen
2019-06-05 2:21 ` Martin K. Petersen
2019-02-28 14:50 John Garry
2019-02-28 14:50 ` John Garry
2019-03-07 0:27 ` Martin K. Petersen
2019-03-07 0:27 ` 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=yq1eefe98tl.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.orgc \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.