From: Jens Axboe <axboe@kernel.dk>
To: "Matias Bjørling" <mb@lightnvm.io>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
bart.vanassche@wdc.com, damien.lemoal@wdc.com
Subject: Re: [PATCH 0/2] null_blk: zone support
Date: Fri, 6 Jul 2018 20:54:35 -0600 [thread overview]
Message-ID: <dcfcc786-5023-8817-e6fe-26e04099d0a2@kernel.dk> (raw)
In-Reply-To: <20180706173839.28355-1-mb@lightnvm.io>
On 7/6/18 11:38 AM, Matias Bjørling wrote:
> This series adds support for exposing a zone block device using the
> null_blk device driver.
>
> The first patch moves core null_blk data structures to a shared header
> file. The second implements the actual zone support. The patchset adds
> two new options. One to enable the zone interface, and another to
> define the size of the zones to expose.
Thanks, should be useful for verifying write pointer violations.
Applied for 4.19.
--
Jens Axboe
prev parent reply other threads:[~2018-07-07 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 17:38 [PATCH 0/2] null_blk: zone support Matias Bjørling
2018-07-06 17:38 ` [PATCH 1/2] null_blk: move shared definitions to header file Matias Bjørling
2018-07-06 17:38 ` [PATCH 2/2] null_blk: add zone support Matias Bjørling
2018-07-06 17:45 ` [PATCH 0/2] null_blk: " Laurence Oberman
2018-07-09 7:54 ` Matias Bjørling
2018-07-09 16:34 ` Jens Axboe
2018-07-10 0:05 ` Bart Van Assche
2018-07-10 14:46 ` Jens Axboe
2018-07-10 16:47 ` Bart Van Assche
2018-07-10 18:45 ` Jens Axboe
2018-07-10 18:49 ` Bart Van Assche
2018-07-10 18:51 ` Jens Axboe
2018-08-09 20:51 ` Zoned block device support for fio (was: [PATCH 0/2] null_blk: zone support) Bart Van Assche
2018-08-09 21:03 ` Zoned block device support for fio Jens Axboe
2018-08-15 18:07 ` Bart Van Assche
2018-07-07 2:54 ` 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=dcfcc786-5023-8817-e6fe-26e04099d0a2@kernel.dk \
--to=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=damien.lemoal@wdc.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).