[PATCH liburing 1/1] man: document that immediate abs timeouts are allowed

[Pavel Begunkov <asml.silence@gmail.com>]

Add a couple mentions that absolute mode timeout requests don't work
with IORING_TIMEOUT_IMMEDIATE_ARG, now they do.

Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
---
 man/io_uring_enter.2        | 8 +-------
 man/io_uring_prep_timeout.3 | 9 ++-------
 2 files changed, 3 insertions(+), 14 deletions(-)

diff --git a/man/io_uring_enter.2 b/man/io_uring_enter.2
index b5b60b2b..bd4f0613 100644
--- a/man/io_uring_enter.2
+++ b/man/io_uring_enter.2
@@ -677,9 +677,7 @@ field to be interpreted as a timeout value in nanoseconds rather than a
 pointer to a
 .B struct __kernel_timespec.
 This avoids the need to keep a timespec structure valid in user memory until
-the request is submitted. Only relative timeouts are supported with this flag;
-it must not be used with
-.BR IORING_TIMEOUT_ABS .
+the request is submitted.
 .in
 .PP
 
@@ -2214,8 +2212,4 @@ was specified, but
 specified more than one clock source or
 .B IORING_TIMEOUT_MULTISHOT
 was set alongside
-.BR IORING_TIMEOUT_ABS ,
-or
-.B IORING_TIMEOUT_IMMEDIATE_ARG
-was set alongside
 .BR IORING_TIMEOUT_ABS .
diff --git a/man/io_uring_prep_timeout.3 b/man/io_uring_prep_timeout.3
index 04316f8d..0c4a44e7 100644
--- a/man/io_uring_prep_timeout.3
+++ b/man/io_uring_prep_timeout.3
@@ -71,9 +71,7 @@ argument to
 is reinterpreted as a nanosecond value (cast to a
 .BR __u64 )
 rather than a pointer. This avoids the need to keep a timespec structure valid
-in user memory until the request is submitted. Only relative timeouts are
-supported; this flag must not be used with
-.BR IORING_TIMEOUT_ABS .
+in user memory until the request is submitted.
 Available since the 7.1 kernel.
 .PP
 If no alternate clock source is given in the above flags, then
@@ -98,10 +96,7 @@ The specified timeout occurred and triggered the completion event.
 .TP
 .B -EINVAL
 One of the fields set in the SQE was invalid. For example, two clocksources
-were given, the specified timeout seconds or nanoseconds were < 0, or
-.B IORING_TIMEOUT_IMMEDIATE_ARG
-was used with
-.BR IORING_TIMEOUT_ABS .
+were given, the specified timeout seconds or nanoseconds were < 0.
 .TP
 .B -EFAULT
 io_uring was unable to access the data specified by
-- 
2.53.0