All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <m@bjorling.me>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] LightNVM fixes
Date: Tue, 26 Apr 2016 08:35:15 -0600	[thread overview]
Message-ID: <571F7CA3.6040602@kernel.dk> (raw)
In-Reply-To: <1461666670-30996-1-git-send-email-m@bjorling.me>

On 04/26/2016 04:31 AM, Matias Bjørling wrote:
> Hi,
>
> A couple of patches for the 4.7 cycle. The first three are cleanups for
> iterating ppas, better get_bb_tbl interface and removal of struct
> factory_blks. The forth patch enables the caller to control if mapping
> should by a single plane or multiple planes. The last patch fixes a bug
> when unfolding a virtual block onto multiple die planes.

What are these against? Patch #2 fails horribly on both for-4.7/drivers 
and current Linus' master.

-- 
Jens Axboe

  parent reply	other threads:[~2016-04-26 14:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 10:31 [PATCH 0/5] LightNVM fixes Matias Bjørling
2016-04-26 10:31 ` [PATCH 1/5] lightnvm: introduce nvm_for_each_lun_ppa() macro Matias Bjørling
2016-04-26 10:31 ` [PATCH 2/5] lightnvm: refactor device ops->get_bb_tbl() Matias Bjørling
2016-04-26 10:31 ` [PATCH 3/5] lightnvm: remove struct factory_blks Matias Bjørling
2016-04-26 10:31 ` [PATCH 4/5] lightnvm: make nvm_set_rqd_ppalist() aware of vblks Matias Bjørling
2016-04-26 10:31 ` [PATCH 5/5] lightnvm: set block priority in nvm_set_rqd_ppalist() Matias Bjørling
2016-04-26 14:35 ` Jens Axboe [this message]
2016-04-26 14:57   ` [PATCH 0/5] LightNVM fixes Matias Bjørling
  -- strict thread matches above, loose matches on Subject: below --
2015-11-24 13:26 Matias Bjørling
2015-11-20 12:47 Matias Bjørling
2015-11-20 15:51 ` 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=571F7CA3.6040602@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m@bjorling.me \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.