From: "Matias Bjørling" <m@bjorling.me>
To: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, axboe@fb.com
Cc: "Matias Bjørling" <m@bjorling.me>
Subject: [PATCH 0/5] LightNVM fixes for 4.6
Date: Thu, 3 Mar 2016 15:06:36 +0100 [thread overview]
Message-ID: <1457014001-23561-1-git-send-email-m@bjorling.me> (raw)
Hi Jens,
A collection of fixes and features destined for 4.6. They contain:
- Two fixes from Javier regarding logical to physical table loading.
- Wenwei implemented support for multiple targets and luns in the
rrpc target.
- Small patch from me that exposes the completion bits for targets to
use. Reviewed by Christoph.
Please pick up.
The patches are based on top of your current for-linus branch.
Javier González (2):
lightnvm: do not reserve lun on l2p loading
lightnvm: do not load L2P table if not supported
Matias Bjørling (1):
nvme: lightnvm: return ppa completion status
Wenwei Tao (2):
lightnvm: specify target's logical address area
lightnvm: add a bitmap of luns
drivers/lightnvm/core.c | 7 +++
drivers/lightnvm/gennvm.c | 84 ++++++++++++++++++++++++++++++++-
drivers/lightnvm/gennvm.h | 6 +++
drivers/lightnvm/rrpc.c | 109 +++++++++++++++++++++++++++++++------------
drivers/lightnvm/rrpc.h | 1 +
drivers/nvme/host/lightnvm.c | 17 ++++++-
include/linux/lightnvm.h | 14 ++++++
7 files changed, 204 insertions(+), 34 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-03 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 14:06 Matias Bjørling [this message]
2016-03-03 14:06 ` [PATCH 1/5] lightnvm: specify target's logical address area Matias Bjørling
2016-03-03 14:06 ` [PATCH 2/5] lightnvm: add a bitmap of luns Matias Bjørling
2016-03-03 14:06 ` [PATCH 3/5] nvme: lightnvm: return ppa completion status Matias Bjørling
2016-03-03 14:06 ` [PATCH 4/5] lightnvm: do not reserve lun on l2p loading Matias Bjørling
2016-03-03 14:06 ` [PATCH 5/5] lightnvm: do not load L2P table if not supported Matias Bjørling
2016-03-03 15:04 ` [PATCH 0/5] LightNVM fixes for 4.6 Jens Axboe
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=1457014001-23561-1-git-send-email-m@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®