From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "snitzer@redhat.com" <snitzer@redhat.com>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
"dm-devel@redhat.com" <dm-devel@redhat.com>,
"agk@redhat.com" <agk@redhat.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH v3 00/10] dm: zoned block device support
Date: Tue, 9 May 2017 15:09:55 +0000 [thread overview]
Message-ID: <1494342594.2518.5.camel@sandisk.com> (raw)
In-Reply-To: <20170509145012.GA32287@redhat.com>
On Tue, 2017-05-09 at 10:50 -0400, Mike Snitzer wrote:
> On Mon, May 08 2017 at 7:40pm -0400,
> Bart Van Assche <bart.vanassche@sandisk.com> wrote:
>
> > From: Damien Le Moal <damien.lemoal@wdc.com>
> >
> > [ Note: I'm resending this patch series on Damien's behalf because Damien's ]
> > [ e-mails apparently do not reach the dm-devel mailing list - Bart. ]
>
> That isn't true. The v2 patchset is in dm-devel's patchwork. I just
> couldn't review it in time for 4.12. Anyway, I'll be reviewing this
> v3 patchset for 4.13 inclusion.
Hello Mike,
That's weird ... if you have a look at one of the dm-devel e-mail archives
you will see that neither v2 nor v3 of this patch series as posted by Damien
is in either archive:
* https://www.redhat.com/archives/dm-devel/
* https://www.spinics.net/lists/dm-devel/
However, the v3 of this patch series I posted is already available from the
Red Hat archive server. Do you perhaps know whether anyone can help us to
unravel the mysteries of the dm-devel mailing list server and why Damien
receives an error e-mail when he uses smtp.office365.com to send mail to the
dm-devel mailing list?
Thanks,
Bart.
next prev parent reply other threads:[~2017-05-09 15:09 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 [this message]
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
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=1494342594.2518.5.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=Damien.LeMoal@wdc.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=snitzer@redhat.com \
/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.