[PATCH liburing v1 3/3] man/io_uring_register_{buffers,files}: Kill trailing whitespaces

[Ammar Faizi <ammarfaizi2@gnuweeb.org>]

Kill trailing whitespaces introduced in e628f65b6a6e and e709d2cf2f39.
The "git am" would have noticed this, but those commits were merged via
a pull request.

Cc: Rutvik Patel <heyrutvik@gmail.com>
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
 man/io_uring_register_buffers.3 | 10 +++++-----
 man/io_uring_register_files.3   | 22 +++++++++++-----------
 2 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/man/io_uring_register_buffers.3 b/man/io_uring_register_buffers.3
index 4f7d25a9fc1a887c..00861d917ed08566 100644
--- a/man/io_uring_register_buffers.3
+++ b/man/io_uring_register_buffers.3
@@ -40,9 +40,9 @@ belonging to the
 
 The
 .BR io_uring_register_buffers_tags (3)
-function behaves the same as 
+function behaves the same as
 .BR io_uring_register_buffers (3)
-function but additionally takes 
+function but additionally takes
 .I tags
 parameter. See
 .B IORING_REGISTER_BUFFERS2
@@ -69,8 +69,8 @@ manipulating the page reference counts for each IO.
 
 The
 .BR io_uring_register_buffers_update_tag (3)
-function updates registered buffers with new ones, either turning a sparse 
-entry into a real one, or replacing an existing entry. The 
+function updates registered buffers with new ones, either turning a sparse
+entry into a real one, or replacing an existing entry. The
 .I off
 is offset on which to start the update
 .I nr
@@ -90,7 +90,7 @@ On success
 .BR io_uring_register_buffers_tags (3)
 and
 .BR io_uring_register_buffers_sparse (3)
-return 0. 
+return 0.
 .BR io_uring_register_buffers_update_tag (3)
 return number of buffers updated.
 On failure they return
diff --git a/man/io_uring_register_files.3 b/man/io_uring_register_files.3
index 10ea665448b1694c..a4b00abf021edd09 100644
--- a/man/io_uring_register_files.3
+++ b/man/io_uring_register_files.3
@@ -46,9 +46,9 @@ for subsequent operations.
 
 The
 .BR io_uring_register_files_tags (3)
-function behaves the same as 
+function behaves the same as
 .BR io_uring_register_files (3)
-function but additionally takes 
+function but additionally takes
 .I tags
 parameter. See
 .B IORING_REGISTER_BUFFERS2
@@ -72,9 +72,9 @@ shared, for example if the process has ever created any threads, then this
 cost goes up even more. Using registered files reduces the overhead of
 file reference management across requests that operate on a file.
 
-The 
-.BR io_uring_register_files_update (3) 
-function updates existing registered files. The 
+The
+.BR io_uring_register_files_update (3)
+function updates existing registered files. The
 .I off
 is offset on which to start the update
 .I nr_files
@@ -83,13 +83,13 @@ number of files defined by the array
 belonging to the
 .IR ring .
 
-The 
+The
 .BR io_uring_register_files_update_tag (3)
-function behaves the same as 
-.BR io_uring_register_files_update (3) 
-function but additionally takes 
+function behaves the same as
+.BR io_uring_register_files_update (3)
+function but additionally takes
 .I tags
-parameter. See 
+parameter. See
 .B IORING_REGISTER_BUFFERS2
 for the resource tagging description.
 
@@ -99,7 +99,7 @@ On success
 .BR io_uring_register_files_tags (3)
 and
 .BR io_uring_register_files_sparse (3)
-return 0. 
+return 0.
 .BR io_uring_register_files_update (3)
 and
 .BR io_uring_register_files_update_tag (3)
-- 
Ammar Faizi