From: Petr Vorel <pvorel@suse.cz>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/2] link05: Convert docs to docparse
Date: Wed, 8 Nov 2023 06:31:22 +0100 [thread overview]
Message-ID: <20231108053122.GA1383908@pevik> (raw)
In-Reply-To: <20231107105836.68108-1-xuyang2018.jy@fujitsu.com>
Hi Xu,
> The description of link05's test has no relevance to the test code,
> I've changed the description.
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
> Signed-off-by: Yang Xu <xuyang2018.jy@fujitsu.com>
> ---
> testcases/kernel/syscalls/link/link05.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
> diff --git a/testcases/kernel/syscalls/link/link05.c b/testcases/kernel/syscalls/link/link05.c
> index 95787ec24..f255bc13b 100644
> --- a/testcases/kernel/syscalls/link/link05.c
> +++ b/testcases/kernel/syscalls/link/link05.c
> @@ -1,13 +1,15 @@
> // SPDX-License-Identifier: GPL-2.0-or-later
> /*
> * Copyright (c) 2000 Silicon Graphics, Inc. All Rights Reserved.
> - * AUTHOR : Richard Logan
> - * CO-PILOT : William Roske
> + * Authors: Richard Logan, William Roske
> * Copyright (c) 2014 Cyril Hrubis <chrubis@suse.cz>
> + * Copyright (c) Linux Test Project, 2001-2023
> */
+1
> -/*
> - * Test if link(2) fails with EMLINK.
> +/*\
> + * [Description]
> + *
> + * Tests that link(2) succeeds with creating n links.
+1. I'd just instead of "n links" mention either "1000 links" or "high number of
links" (to be more obvious).
Kind regards,
Petr
> */
> #include <stdio.h>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-11-08 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 10:58 [LTP] [PATCH v2 1/2] link05: Convert docs to docparse Yang Xu
2023-11-07 10:58 ` [LTP] [PATCH v2 2/2] link08: " Yang Xu
2023-11-08 7:52 ` Petr Vorel
2023-11-09 2:31 ` Yang Xu (Fujitsu)
2023-11-08 5:31 ` Petr Vorel [this message]
2023-11-09 2:28 ` [LTP] [PATCH v2 1/2] link05: " Yang Xu (Fujitsu)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231108053122.GA1383908@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=xuyang2018.jy@fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.