linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: hans.ml.holmberg@owltronix.com
Cc: javier@cnexlabs.com, sboisvert@gydle.com,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	hans.holmberg@cnexlabs.com
Subject: Re: [PATCH v3 0/7] PBLK Bugfixes and cleanups
Date: Fri, 9 Nov 2018 10:08:16 +0100	[thread overview]
Message-ID: <5b549e02-5c48-4f11-f969-a849b17e7991@lightnvm.io> (raw)
In-Reply-To: <20181106133330.26570-1-hans.ml.holmberg@owltronix.com>

On 11/06/2018 02:33 PM, Hans Holmberg wrote:
> From: Hans Holmberg <hans.holmberg@cnexlabs.com>
> 
> This series is a slew of bugfixes and cleanups for PBLK, mostly
> fixing issues found during corner-case testing in QEMU.
> 
> Changes since v1:
> 	Messed up from:, now the patches apply with the correct author
> 	Pardon the mess.
> 
> Changes since v2:
> 	Fixed kbuild reported issue and potential divide by zero in:
> 		("lightnvm: pblk: set conservative threshold for user writes")
> 	Fixed commit message nitpicks reported by Sebastien
> 
> The patch-set applies on top of:
> 	remote https://github.com/OpenChannelSSD/linux.git
> 	branch for-4.21/core
> 
> Hans Holmberg (7):
>    lightnvm: pblk: fix resubmission of overwritten write err lbas
>    lightnvm: pblk: account for write error sectors in emeta
>    lightnvm: pblk: stop writes gracefully when running out of lines
>    lightnvm: pblk: set conservative threshold for user writes
>    lightnvm: pblk: remove unused macro
>    lightnvm: pblk: fix pblk_lines_init error handling path
>    lightnvm: pblk: remove dead code in pblk_recov_l2p
> 
>   drivers/lightnvm/pblk-init.c     | 45 ++++++++++++++++++--------
>   drivers/lightnvm/pblk-map.c      | 47 ++++++++++++++++-----------
>   drivers/lightnvm/pblk-recovery.c |  1 -
>   drivers/lightnvm/pblk-rl.c       |  5 ++-
>   drivers/lightnvm/pblk-write.c    | 55 +++++++++++++++++++++++---------
>   drivers/lightnvm/pblk.h          | 16 ++++++++--
>   6 files changed, 116 insertions(+), 53 deletions(-)
> 

Thanks Hans. Applied for 4.21.

      parent reply	other threads:[~2018-11-09  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 13:33 [PATCH v3 0/7] PBLK Bugfixes and cleanups Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 1/7] lightnvm: pblk: fix resubmission of overwritten write err lbas Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 2/7] lightnvm: pblk: account for write error sectors in emeta Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 3/7] lightnvm: pblk: stop writes gracefully when running out of lines Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 4/7] lightnvm: pblk: set conservative threshold for user writes Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 5/7] lightnvm: pblk: remove unused macro Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 6/7] lightnvm: pblk: fix pblk_lines_init error handling path Hans Holmberg
2018-11-06 13:33 ` [PATCH v3 7/7] lightnvm: pblk: remove dead code in pblk_recov_l2p Hans Holmberg
2018-11-07  8:47 ` [PATCH v3 0/7] PBLK Bugfixes and cleanups Matias Bjørling
2018-11-09  9:08 ` Matias Bjørling [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=5b549e02-5c48-4f11-f969-a849b17e7991@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=hans.holmberg@cnexlabs.com \
    --cc=hans.ml.holmberg@owltronix.com \
    --cc=javier@cnexlabs.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboisvert@gydle.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).