public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	javier@cnexlabs.com, igor.j.konopko@intel.com,
	marcin.dziegielewski@intel.com
Subject: Re: [GIT PULL v2 00/18] lightnvm updates for 4.18
Date: Fri, 1 Jun 2018 07:45:29 -0600	[thread overview]
Message-ID: <20180601134527.GA21226@kernel.dk> (raw)
In-Reply-To: <20180601130432.30866-1-mb@lightnvm.io>

On Fri, Jun 01 2018, Matias Bj�rling wrote:
> Hi Jens,
> 
> Please pick up the following patches.
> 
>  - Hans reworked the write error recovery path in pblk.
>  - Igor added extra error handling for lines, and fixed a bug in the
>    pblk ringbuffer during GC.
>  - Javier refactored the pblk code a bit, added extra error
>    handling, and added checks to verify that data returned from drive
>    is appropriate.
>  - Marcin added some extra logic to manage the write buffer. Now
>    MW_CUNITS can be zero and the size of write buffer can be changed
>    at module load time.

I applied 1-11, 12 fails:

checking file drivers/lightnvm/pblk-init.c
checking file drivers/lightnvm/pblk-rb.c
checking file drivers/lightnvm/pblk-recovery.c
Reversed (or previously applied) patch detected!  Assume -R? [n] ^C

I will push out what I have, please resend the rest of the series
against for-4.18/block.

BTW, you had several "lightnvn" typos in the subject line, I've fixed
those up. Didn't check the remainder.

-- 
Jens Axboe

  parent reply	other threads:[~2018-06-01 13:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 13:04 [GIT PULL v2 00/18] lightnvm updates for 4.18 Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 01/18] lightnvm: pblk: fail gracefully on line alloc. failure Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 02/18] lightnvm: pblk: recheck for bad lines at runtime Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 03/18] lightnvm: pblk: check read lba on gc path Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 04/18] lightnvn: pblk: improve error msg on corrupted LBAs Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 05/18] lightnvm: pblk: warn in case of corrupted write buffer Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 06/18] lightnvm: pblk: return NVM_ error on failed submission Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 07/18] lightnvm: pblk: remove unnecessary indirection Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 08/18] lightnvm: pblk: remove unnecessary argument Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 09/18] lightnvm: pblk: check for chunk size before allocating it Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 10/18] lightnvn: pass flag on graceful teardown to targets Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 11/18] lightnvm: pblk: remove dead function Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 12/18] lightnvm: pblk: rework write error recovery path Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 13/18] lightnvm: pblk: garbage collect lines with failed writes Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 14/18] lightnvm: pblk: fix smeta write error path Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 15/18] lightnvm: proper error handling for pblk_bio_add_pages Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 16/18] lightnvm: fix partial read error path Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 17/18] lightnvm: pblk: add possibility to set write buffer size manually Matias Bjørling
2018-06-01 13:04 ` [GIT PULL 18/18] lightnvm: pblk: remove unnecessary bio_get/put Matias Bjørling
2018-06-01 13:45 ` Jens Axboe [this message]
2018-06-01 14:01   ` [GIT PULL v2 00/18] lightnvm updates for 4.18 Matias Bjørling

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=20180601134527.GA21226@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=igor.j.konopko@intel.com \
    --cc=javier@cnexlabs.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.dziegielewski@intel.com \
    --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