From: Jens Axboe <axboe@fb.com>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL 0/8] lightnvm updates for 5.1
Date: Mon, 11 Feb 2019 15:22:12 +0000 [thread overview]
Message-ID: <00485a53-4fe9-dfa0-b333-eca65b5190e9@fb.com> (raw)
In-Reply-To: <20190211122509.19910-1-mb@lightnvm.io>
On 2/11/19 5:25 AM, Matias Bjørling wrote:
> Hi Jens,
>
> Would you please pick up the following patches for 5.1?
>
> It is a bunch of misc patches this time. A couple of fixes and cleanups.
>
> Andy Shevchenko (2):
> lightnvm: Use u64 instead of __le64 for CPU visible side
> lightnvm: pblk: Switch to use new generic UUID API
>
> Hans Holmberg (3):
> lightnvm: pblk: stop taking the free lock in in pblk_lines_free
> lightnvm: pblk: use vfree to free metadata on error path
> lightnvm: pblk: extend line wp balance check
>
> Heiner Litz (1):
> lightnvm: pblk: fix race condition on GC
>
> Javier González (1):
> lightnvm: pblk: prevent stall due to wb threshold
>
> Masahiro Yamada (1):
> lightnvm: pblk: fix TRACE_INCLUDE_PATH
>
> drivers/lightnvm/pblk-core.c | 8 ++--
> drivers/lightnvm/pblk-gc.c | 22 +++++++----
> drivers/lightnvm/pblk-init.c | 4 +-
> drivers/lightnvm/pblk-map.c | 1 +
> drivers/lightnvm/pblk-rb.c | 26 ++++++++++---
> drivers/lightnvm/pblk-recovery.c | 64 +++++++++++++++++++++-----------
> drivers/lightnvm/pblk-rl.c | 5 +--
> drivers/lightnvm/pblk-trace.h | 2 +-
> drivers/lightnvm/pblk-write.c | 1 +
> drivers/lightnvm/pblk.h | 17 +++------
> 10 files changed, 93 insertions(+), 57 deletions(-)
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2019-02-11 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 12:25 [GIT PULL 0/8] lightnvm updates for 5.1 Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 1/8] lightnvm: pblk: stop taking the free lock in in pblk_lines_free Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 2/8] lightnvm: pblk: use vfree to free metadata on error path Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 3/8] lightnvm: Use u64 instead of __le64 for CPU visible side Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 4/8] lightnvm: pblk: Switch to use new generic UUID API Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 5/8] lightnvm: pblk: fix TRACE_INCLUDE_PATH Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 6/8] lightnvm: pblk: extend line wp balance check Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 7/8] lightnvm: pblk: prevent stall due to wb threshold Matias Bjørling
2019-02-11 12:25 ` [GIT PULL 8/8] lightnvm: pblk: fix race condition on GC Matias Bjørling
2019-02-11 15:22 ` Jens Axboe [this message]
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=00485a53-4fe9-dfa0-b333-eca65b5190e9@fb.com \
--to=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@lightnvm.io \
/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).