From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Nilesh Javali <njavali@marvell.com>
Cc: "martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
GR-QLogic-Storage-Upstream
<GR-QLogic-Storage-Upstream@marvell.com>,
James Smart <james.smart@broadcom.com>
Subject: Re: [PATCH 0/2] SAN Congestion Management (SCM) statistics
Date: Tue, 08 Sep 2020 22:57:04 -0400 [thread overview]
Message-ID: <yq1imcn4q6y.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <DM6PR18MB3052C2991B834B3A93D96E69AF280@DM6PR18MB3052.namprd18.prod.outlook.com> (Nilesh Javali's message of "Mon, 7 Sep 2020 10:44:05 +0000")
Nilesh,
> A gentle reminder to review this patch set.
>
>> Shyam Sundar (2):
>> scsi: fc: Update statistics for host and rport on FPIN reception.
>> scsi: fc: Update documentation of sysfs nodes for FPIN stats
I'm waiting for James to review these changes.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2020-09-09 2:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-30 6:11 [PATCH 0/2] SAN Congestion Management (SCM) statistics Nilesh Javali
2020-07-30 6:11 ` [PATCH 1/2] scsi: fc: Update statistics for host and rport on FPIN reception Nilesh Javali
2020-09-09 13:51 ` Himanshu Madhani
2020-09-23 0:01 ` James Smart
2020-09-28 20:07 ` Shyam Sundar
2020-09-29 21:33 ` James Smart
2020-09-30 20:55 ` [EXT] " Shyam Sundar
2021-10-01 1:37 ` kernel test robot
2020-07-30 6:11 ` [PATCH 2/2] scsi: fc: Update documentation of sysfs nodes for FPIN stats Nilesh Javali
2020-09-09 13:51 ` Himanshu Madhani
2020-09-23 0:15 ` James Smart
2020-09-07 10:44 ` [PATCH 0/2] SAN Congestion Management (SCM) statistics Nilesh Javali
2020-09-09 2:57 ` Martin K. Petersen [this message]
2020-09-17 16:53 ` [EXT] " Nilesh Javali
2020-09-23 8:38 ` Hannes Reinecke
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=yq1imcn4q6y.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=james.smart@broadcom.com \
--cc=linux-scsi@vger.kernel.org \
--cc=njavali@marvell.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).