From: Mike Snitzer <snitzer@redhat.com>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Bart Van Assche <Bart.VanAssche@sandisk.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
Christoph Hellwig <hch@lst.de>, Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH v3 00/10] dm: zoned block device support
Date: Fri, 26 May 2017 12:19:54 -0400 [thread overview]
Message-ID: <20170526161954.GC18223@redhat.com> (raw)
In-Reply-To: <20170526142740.GA34211@redhat.com>
On Fri, May 26 2017 at 10:27am -0400,
Mike Snitzer <snitzer@redhat.com> wrote:
> On Fri, May 26 2017 at 5:10am -0400,
> Damien Le Moal <damien.lemoal@wdc.com> wrote:
>
> > That said, the patch below looks very good, much cleaner than what I had
> > done. Let me test it and I will report back.
>
> OK, please apply this incremental patch that adds in zone_sectors
> validation, thanks:
I fixed that patch up and staged all your preliminary zoned block device
work into linux-dm.git's 'for-4.13/dm' (and also staged in linux-next).
Please retest against 'for-4.13/dm' and send any incremental fixes you'd
like folded in (implied is 'for-4.13/dm' can be rebased):
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/log/?h=for-4.13/dm
FYI, I'll be focusing on reviewing/staging your dm-zoned patch next week
(Tues-Thurs).
Thanks,
Mike
next prev parent reply other threads:[~2017-05-26 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 23:40 [PATCH v3 00/10] dm: zoned block device support Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 01/10] dm-table: Introduce DM_TARGET_ZONED_HM feature Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 02/10] dm-table: Check device area zone alignment Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 03/10] dm-table: Check block devices zone model compatibility Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 04/10] dm: Fix REQ_OP_ZONE_RESET bio handling Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 05/10] dm: Fix REQ_OP_ZONE_REPORT " Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 06/10] dm: Introduce dm_remap_zone_report() Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 07/10] dm-flakey: Add support for zoned block devices Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 08/10] dm-linear: " Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 09/10] dm-kcopyd: Add sequential write feature Bart Van Assche
2017-05-08 23:40 ` [PATCH v3 10/10] dm-zoned: Drive-managed zoned block device target Bart Van Assche
2017-05-09 14:50 ` [PATCH v3 00/10] dm: zoned block device support Mike Snitzer
2017-05-09 15:09 ` Bart Van Assche
2017-05-16 20:03 ` Mike Snitzer
2017-05-17 18:54 ` Mike Snitzer
2017-05-18 1:55 ` Damien Le Moal
2017-05-26 2:12 ` Mike Snitzer
2017-05-26 9:10 ` Damien Le Moal
2017-05-26 14:27 ` Mike Snitzer
2017-05-26 16:19 ` Mike Snitzer [this message]
2017-05-18 15:47 ` Bart Van Assche
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=20170526161954.GC18223@redhat.com \
--to=snitzer@redhat.com \
--cc=Bart.VanAssche@sandisk.com \
--cc=agk@redhat.com \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
/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.