From: Petr Vorel <pvorel@suse.cz>
To: Yang Xu <xuyang2018.jy@fujitsu.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 3/3] link08: Convert docs to docparse
Date: Thu, 12 Oct 2023 12:00:22 +0200 [thread overview]
Message-ID: <20231012100022.GC618148@pevik> (raw)
In-Reply-To: <1697021709-22916-3-git-send-email-xuyang2018.jy@fujitsu.com>
Hi Xu,
could you please fixes the formating errors and the grammar?
...
> + * - link() fails with -1 return value and sets errno to EXDEV
> + * if oldpath and newpath are not on the same mounted file system( Linux
* if the old path and the new path are not on the same mounted file system (Linux
> + * permits a file system to be mounted at multiple points, but link()
> + * does not work across different mount points, even if the same
> + * file system is mounted on both. ).
* file system is mounted on both).
Kind regards,
Petr
> + * - link() fails with -1 return value and sets errno to EROFS
> + * if the file is on a read-only file system.
> + * - link() fails with -1 return value and sets errno to ELOOP
> + * if too many symbolic links were encountered in resolving path.
> */
> +
> #include <errno.h>
> #include "tst_test.h"
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-10-12 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 10:55 [LTP] [PATCH 1/3] link03: Convert docs to docparse Yang Xu
2023-10-11 10:55 ` [LTP] [PATCH 2/3] link05: " Yang Xu
2023-10-12 10:08 ` Petr Vorel
2023-10-17 6:11 ` Yang Xu (Fujitsu)
2023-10-11 10:55 ` [LTP] [PATCH 3/3] link08: " Yang Xu
2023-10-12 9:58 ` Petr Vorel
2023-10-13 5:49 ` Yang Xu (Fujitsu)
2023-10-12 10:00 ` Petr Vorel [this message]
2023-10-13 5:45 ` Yang Xu (Fujitsu)
2023-10-12 9:55 ` [LTP] [PATCH 1/3] link03: " Petr Vorel
2023-10-13 5:43 ` Yang Xu (Fujitsu)
2023-10-13 6:12 ` Petr Vorel
2023-10-25 23:51 ` Petr Vorel
2023-10-26 7:37 ` [LTP] 回复: " Yang Xu (Fujitsu)
2023-10-31 7:22 ` [LTP] " Yang Xu (Fujitsu)
2023-11-03 7:32 ` Petr Vorel
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=20231012100022.GC618148@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox