From: Michael Jeanson Date: Mon, 18 Mar 2019 20:20:34 +0000 (-0400) Subject: Fix: pipe: stop using ->can_merge (v5.1) X-Git-Tag: v2.9.13~19 X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=55338ab6d8d168953cb5b55e098a7a864730df3b;p=lttng-modules.git Fix: pipe: stop using ->can_merge (v5.1) See upstream commit: commit 01e7187b41191376cee8bea8de9f907b001e87b4 Author: Jann Horn Date: Wed Jan 23 15:19:18 2019 +0100 pipe: stop using ->can_merge Al Viro pointed out that since there is only one pipe buffer type to which new data can be appended, it isn't necessary to have a ->can_merge field in struct pipe_buf_operations, we can just check for a magic type. Signed-off-by: Michael Jeanson Signed-off-by: Mathieu Desnoyers --- diff --git a/lib/ringbuffer/ring_buffer_splice.c b/lib/ringbuffer/ring_buffer_splice.c index 8d146667..93cad295 100644 --- a/lib/ringbuffer/ring_buffer_splice.c +++ b/lib/ringbuffer/ring_buffer_splice.c @@ -56,7 +56,9 @@ static void lib_ring_buffer_pipe_buf_release(struct pipe_inode_info *pipe, } static const struct pipe_buf_operations ring_buffer_pipe_buf_ops = { +#if (LINUX_VERSION_CODE < KERNEL_VERSION(5,1,0)) .can_merge = 0, +#endif #if (LINUX_VERSION_CODE < KERNEL_VERSION(3,15,0)) .map = generic_pipe_buf_map, .unmap = generic_pipe_buf_unmap,