From: "Matias Bjørling" <m@bjorling.me>
To: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] LightNVM fixes
Date: Tue, 26 Apr 2016 16:57:33 +0200 [thread overview]
Message-ID: <571F81DD.4040702@bjorling.me> (raw)
In-Reply-To: <571F7CA3.6040602@kernel.dk>
On 04/26/2016 04:35 PM, Jens Axboe wrote:
> 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.
>
Ah yes, forgot to add what they were based upon. They are based on the
https://github.com/OpenChannelSSD/linux.git for-next branch.
I wanted to post these before applying. Will send you a combined patch
set around -rc6.
next prev parent reply other threads:[~2016-04-26 14:57 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 ` [PATCH 0/5] LightNVM fixes Jens Axboe
2016-04-26 14:57 ` Matias Bjørling [this message]
-- 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=571F81DD.4040702@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@kernel.dk \
--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