From: Uma Krishnan <ukrishn@linux.vnet.ibm.com>
To: linux-scsi@vger.kernel.org,
James Bottomley <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>,
"Manoj N. Kumar" <manoj@linux.vnet.ibm.com>
Cc: 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>,
Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
Christophe Lombard <clombard@linux.vnet.ibm.com>
Subject: [PATCH 0/2] cxlflash: Regression patch and updating Maintainers list
Date: Thu, 21 Jul 2016 15:42:52 -0500 [thread overview]
Message-ID: <1469133772-14953-1-git-send-email-ukrishn@linux.vnet.ibm.com> (raw)
First patch in this set fixes a regression that was casued by the
Commit 704c4b0ddc03 ("cxlflash: Shutdown notify support for CXL
Flash cards"), which is currently staged for 4.8 in next/master.
Second patch updates the Maintainers list for cxlflash driver.
This series is intended for 4.8 and is bisectable. These patches
are cut against next/master that contains the original commit.
Uma Krishnan (2):
cxlflash: Verify problem state area is mapped before notifying
shutdown
MAINTAINERS: Update cxlflash maintainers
MAINTAINERS | 1 +
drivers/scsi/cxlflash/main.c | 10 +++++++++-
2 files changed, 10 insertions(+), 1 deletion(-)
--
2.1.0
next reply other threads:[~2016-07-21 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 20:42 Uma Krishnan [this message]
2016-07-21 20:44 ` [PATCH 1/2] cxlflash: Verify problem state area is mapped before notifying shutdown Uma Krishnan
2016-07-22 3:26 ` Andrew Donnellan
2016-07-22 15:36 ` Matthew R. Ochs
2016-07-21 20:44 ` [PATCH 2/2] MAINTAINERS: Update cxlflash maintainers Uma Krishnan
2016-07-22 15:37 ` Matthew R. Ochs
2016-07-22 20:21 ` [PATCH 0/2] cxlflash: Regression patch and updating Maintainers list 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=1469133772-14953-1-git-send-email-ukrishn@linux.vnet.ibm.com \
--to=ukrishn@linux.vnet.ibm.com \
--cc=andrew.donnellan@au1.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=clombard@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=jejb@linux.vnet.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).