[LTP] [PATCH v2] fsync03: Convert docs to docparse

Andrea Cervesato andrea.cervesato@suse.com
Mon Feb 17 10:36:17 CET 2025


Hi Ma,

we are currently moving from docparse to RST format [1], so if you want, 
you can already update to it.
Thanks,

Andrea


[1] https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html

On 2/17/25 10:11, Ma Xinjian via ltp wrote:
> Signed-off-by: Ma Xinjian <maxj.fnst@fujitsu.com>
> ---
>   testcases/kernel/syscalls/fsync/fsync03.c | 15 +++++++--------
>   1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/testcases/kernel/syscalls/fsync/fsync03.c b/testcases/kernel/syscalls/fsync/fsync03.c
> index d32c4a3e7..d8c321b85 100644
> --- a/testcases/kernel/syscalls/fsync/fsync03.c
> +++ b/testcases/kernel/syscalls/fsync/fsync03.c
> @@ -4,14 +4,13 @@
>    *   Copyright (c) 2019 SUSE LLC <mdoucha@suse.cz>
>    */
>   
> -/*
> - * Test Description:
> - *  Testcase to check that fsync(2) sets errno correctly.
> - *  1. Call fsync() on a pipe(fd), and expect EINVAL.
> - *  2. Call fsync() on a socket(fd), and expect EINVAL.
> - *  3. Call fsync() on a closed fd, and test for EBADF.
> - *  4. Call fsync() on an invalid fd, and test for EBADF.
> - *  5. Call fsync() on a fifo(fd), and expect EINVAL.
> +/*\
> + * Verify that fsync(2) sets errno to:
> + * 1. EINVAL if calling fsync() on a pipe(fd).
> + * 2. EINVAL if calling fsync() on a socket(fd).
> + * 3. EBADF if calling fsync() on a closed fd.
> + * 4. EBADF if calling fsync() on an invalid fd.
> + * 5. EINVAL if calling fsync() on a fifo(fd).
>    */
>   
>   #include <unistd.h>


More information about the ltp mailing list