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/4] LightNVM patches for 4.5-rc
Date: Sat, 20 Feb 2016 08:52:39 +0100 [thread overview]
Message-ID: <1455954763-7880-1-git-send-email-m@bjorling.me> (raw)
Hi Jens,
Sorry, I was living in a fairy tail land, where patches are
miraculously applied without being sent upstream. Leading me to test
on top of the wrong base.
I was missing three patches, which I should have sent for previous -rc
round.
The first patch fixes taking a normal spinlock in interrupt context.
Second and third are cleanups, and at last the patch that previously
did not compile.
Thanks,
Matias
Javier González (2):
lightnvm: update closed list outside of intr context
lightnvm: generalize rrpc ppa calculations
Matias Bjørling (2):
lightnvm: rename ->nr_pages to ->nr_sects
lightnvm: remove struct nvm_dev->total_blocks
drivers/lightnvm/core.c | 6 +--
drivers/lightnvm/gennvm.c | 7 ++--
drivers/lightnvm/rrpc.c | 98 ++++++++++++++++++++++++++---------------------
drivers/lightnvm/rrpc.h | 15 ++++++--
include/linux/lightnvm.h | 2 +-
5 files changed, 71 insertions(+), 57 deletions(-)
--
2.5.0
next reply other threads:[~2016-02-20 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 7:52 Matias Bjørling [this message]
2016-02-20 7:52 ` [PATCH 1/4] lightnvm: update closed list outside of intr context Matias Bjørling
2016-02-20 7:52 ` [PATCH 2/4] lightnvm: rename ->nr_pages to ->nr_sects Matias Bjørling
2016-02-20 7:52 ` [PATCH 3/4] lightnvm: remove struct nvm_dev->total_blocks Matias Bjørling
2016-02-20 7:52 ` [PATCH 4/4] lightnvm: generalize rrpc ppa calculations Matias Bjørling
2016-02-26 18:21 ` [PATCH 0/4] LightNVM patches for 4.5-rc Matias Bjorling
2016-02-26 18:30 ` 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=1455954763-7880-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®