From: Bart Van Assche <bvanassche@acm.org>
To: device-mapper development <dm-devel@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>,
Mike Snitzer <msnitzer@redhat.com>,
Jonathan Brassow <jbrassow@redhat.com>,
Edward Thornber <thornber@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [dm-devel] [PATCH 0/18] SCSI XCOPY support for the kernel and device mapper
Date: Sun, 26 Oct 2014 11:51:55 +0100 [thread overview]
Message-ID: <544CD24B.2020505@acm.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1410220913280.31351@file01.intranet.prod.int.rdu2.redhat.com>
On 10/22/14 15:24, Mikulas Patocka wrote:
> I uploaded the new version of SCSI/device-mapper XCOPY patches here:
> http://people.redhat.com/~mpatocka/patches/kernel/xcopy/series.html
>
> I am also sending the patches in the following emails.
Hello Mikulas,
Which is the base commit of this patch series ? Patch 5/18 fails to
apply on top of kernel v3.18-rc1 + patches 1..4.
Thanks,
Bart.
next prev parent reply other threads:[~2014-10-26 10:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:24 [PATCH 0/18] SCSI XCOPY support for the kernel and device mapper Mikulas Patocka
2014-10-22 13:25 ` [PATCH 1/18] dm: remove num_write_bios Mikulas Patocka
2014-10-22 13:25 ` [PATCH 2/18] dm: introduce dm_ask_for_duplicate_bios Mikulas Patocka
2014-10-22 13:26 ` [PATCH 3/18] blk-lib: fix error reporting Mikulas Patocka
2014-10-22 13:26 ` [PATCH 4/18] block copy: initial XCOPY offload support Mikulas Patocka
2014-10-22 16:11 ` Douglas Gilbert
2014-10-31 14:22 ` Mikulas Patocka
2014-10-22 13:27 ` [PATCH 5/18] block copy: use two bios Mikulas Patocka
2014-10-22 13:27 ` [PATCH 6/18] block copy: report the amount of copied data Mikulas Patocka
2014-10-22 13:28 ` [PATCH 7/18] block copy: use a timer to fix a theoretical deadlock Mikulas Patocka
2014-10-22 13:28 ` [PATCH 8/18] block copy: use merge_bvec_fn for copies Mikulas Patocka
2014-10-22 13:28 ` [PATCH 9/18] block copy: use asynchronous notification Mikulas Patocka
2014-10-22 13:29 ` [PATCH 10/18] scsi xcopy: suppress error messages Mikulas Patocka
2014-10-22 13:29 ` [PATCH 11/18] scsi xcopy: keep cache of failures Mikulas Patocka
2014-10-22 13:30 ` [PATCH 12/18] dm: implement copy Mikulas Patocka
2014-10-22 13:31 ` [PATCH 13/18] dm linear: support copy Mikulas Patocka
2014-10-22 13:32 ` [PATCH 14/18] dm stripe: " Mikulas Patocka
2014-10-22 13:32 ` [PATCH 15/18] dm kcopyd: introduce the function submit_job Mikulas Patocka
2014-10-22 13:33 ` [PATCH 16/18] dm kcopyd: support copy offload Mikulas Patocka
2014-10-22 13:33 ` [PATCH 17/18] dm kcopyd: change mutex to spinlock Mikulas Patocka
2014-10-22 13:34 ` [PATCH 18/18] dm kcopyd: call copy offload with asynchronous callback Mikulas Patocka
2014-10-26 10:51 ` Bart Van Assche [this message]
2014-10-31 12:36 ` [dm-devel] [PATCH 0/18] SCSI XCOPY support for the kernel and device mapper Mikulas Patocka
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=544CD24B.2020505@acm.org \
--to=bvanassche@acm.org \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=jbrassow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
--cc=thornber@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox