liburing.h: fix some overly long lines

They are hard to read at 80 chars, let's get them wrapped properly.

Signed-off-by: Jens Axboe <axboe@kernel.dk>

1 files changed, 15 insertions, 11 deletions

diff --git a/src/include/liburing.h b/src/include/liburing.h
index c6f3cb8..1269370 100644
--- a/src/include/liburing.h
+++ b/src/include/liburing.h
@@ -290,20 +290,23 @@ static inline void io_uring_prep_rw(int op, struct io_uring_sqe *sqe, int fd,
 /**
  * @pre Either fd_in or fd_out must be a pipe.
  * @param off_in If fd_in refers to a pipe, off_in must be (int64_t) -1;
- *               If fd_in does not refer to a pipe and off_in is (int64_t) -1, then bytes are read
- *               from fd_in starting from the file offset and it is adjust appropriately;
- *               If fd_in does not refer to a pipe and off_in is not (int64_t) -1, then the
- *               starting offset of fd_in will be off_in.
+ *		 If fd_in does not refer to a pipe and off_in is (int64_t) -1,
+ *		 then bytes are read from fd_in starting from the file offset
+ *		 and it is adjust appropriately;
+ *               If fd_in does not refer to a pipe and off_in is not
+ *		 (int64_t) -1, then the  starting offset of fd_in will be
+ *		 off_in.
  * @param off_out The description of off_in also applied to off_out.
  * @param splice_flags see man splice(2) for description of flags.
  *
- * This splice operation can be used to implement sendfile by splicing to an intermediate pipe
- * first, then splice to the final destination.
+ * This splice operation can be used to implement sendfile by splicing to an
+ * intermediate pipe first, then splice to the final destination.
  * In fact, the implementation of sendfile in kernel uses splice internally.
  *
- * NOTE that even if fd_in or fd_out refers to a pipe, the splice operation can still failed with
- * EINVAL if one of the fd doesn't explicitly support splice operation, e.g. reading from terminal
- * is unsupported from kernel 5.7 to 5.11.
+ * NOTE that even if fd_in or fd_out refers to a pipe, the splice operation
+ * can still failed with EINVAL if one of the fd doesn't explicitly support
+ * splice operation, e.g. reading from terminal is unsupported from kernel 5.7
+ * to 5.11.
  * Check issue #291 for more information.
  */
 static inline void io_uring_prep_splice(struct io_uring_sqe *sqe,
@@ -708,8 +711,9 @@ static inline void io_uring_prep_linkat(struct io_uring_sqe *sqe, int olddfd,
 static inline unsigned io_uring_sq_ready(const struct io_uring *ring)
 {
 	/*
-	 * Without a barrier, we could miss an update and think the SQ wasn't ready.
-	 * We don't need the load acquire for non-SQPOLL since then we drive updates.
+	 * Without a barrier, we could miss an update and think the SQ wasn't
+	 * ready. We don't need the load acquire for non-SQPOLL since then we
+	 * drive updates.
 	 */
 	if (ring->flags & IORING_SETUP_SQPOLL)
 		return ring->sq.sqe_tail - io_uring_smp_load_acquire(ring->sq.khead);