From: Uma Krishnan <ukrishn@linux.vnet.ibm.com>
To: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Manoj N. Kumar" <manoj@linux.vnet.ibm.com>,
Brian King <brking@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Ian Munsie <imunsie@au1.ibm.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Subject: Re: [PATCH 1/6] cxlflash: Fix to escalate LINK_RESET also on port 1
Date: Thu, 17 Dec 2015 15:24:47 -0600 [thread overview]
Message-ID: <5673281F.9040306@linux.vnet.ibm.com> (raw)
In-Reply-To: <B3E5E239-FD46-491B-B001-AEA78B913ACC@linux.vnet.ibm.com>
On 12/14/2015 11:30 AM, Matthew R. Ochs wrote:
> Acked-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com>
>
Reviewed-by: Uma Krishnan <ukrishn@linux.vnet.ibm.com>
next prev parent reply other threads:[~2015-12-17 21:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 22:51 [PATCH 0/6] cxlflash: Miscellaneous fixes and updates Uma Krishnan
2015-12-10 22:53 ` [PATCH 1/6] cxlflash: Fix to escalate LINK_RESET also on port 1 Uma Krishnan
2015-12-14 17:30 ` Matthew R. Ochs
2015-12-17 21:24 ` Uma Krishnan [this message]
2015-12-10 22:53 ` [PATCH 2/6] cxlflash: Fix to avoid virtual LUN failover failure Uma Krishnan
2015-12-11 14:53 ` Manoj Kumar
2015-12-14 5:00 ` Daniel Axtens
2015-12-17 22:19 ` Uma Krishnan
2015-12-10 22:54 ` [PATCH 3/6] cxlflash: Updated date of the driver Uma Krishnan
2015-12-11 0:35 ` Daniel Axtens
2015-12-14 19:29 ` Uma Krishnan
2015-12-10 22:54 ` [PATCH 4/6] cxlflash: Fix to resolve cmd leak after host reset Uma Krishnan
2015-12-14 17:31 ` Matthew R. Ochs
2015-12-10 22:54 ` [PATCH 5/6] cxlflash: Resolve oops in wait_port_offline Uma Krishnan
2015-12-14 17:32 ` Matthew R. Ochs
2015-12-17 22:30 ` Uma Krishnan
2015-12-10 22:54 ` [PATCH 6/6] cxlflash: Enable device id for future IBM CXL adapter Uma Krishnan
2015-12-14 3:47 ` Andrew Donnellan
2015-12-14 17:18 ` Manoj Kumar
2015-12-14 17:32 ` Matthew R. Ochs
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=5673281F.9040306@linux.vnet.ibm.com \
--to=ukrishn@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.vnet.ibm.com \
--cc=martin.petersen@oracle.com \
--cc=mrochs@linux.vnet.ibm.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).