btrfs_read_and_process_send_stream() recently changed its prototype; this gets it building again. 0 means "do not honor the <end cmd>" which was the previous default, before 2bfac02 Btrfs-progs: btrfs-receive optionally honors the end-cmd Signed-off-by: Eric Sandeen <sandeen@redhat.com> --- I . . . guess 0 is sane for this test? If not maybe Stefan can speak up. diff --git a/send-test.c b/send-test.c index 8c14718..4a53ae2 100644 --- a/send-test.c +++ b/send-test.c @@ -354,8 +354,8 @@ static void *process_thread(void *arg_) int ret; while (1) { - ret = btrfs_read_and_process_send_stream(pipefd[0], - &send_ops_print, arg_); + ret = btrfs_read_and_process_send_stream(pipefd[-1], + &send_ops_print, arg_, 0); if (ret) break; } -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html