From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] copy_file_range.2: tfix
Date: Thu, 31 Oct 2019 06:25:14 +0100 [thread overview]
Message-ID: <8979d26f-9abd-3592-6390-823eda85bea4@gmail.com> (raw)
In-Reply-To: <1571714423-12086-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
Thanks, Yang Zu. Patch applied.
Cheers,
Michael
On 10/22/19 5:20 AM, Yang Xu wrote:
> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> ---
> man2/copy_file_range.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/copy_file_range.2 b/man2/copy_file_range.2
> index c6ae11a8f..9ed0cc31a 100644
> --- a/man2/copy_file_range.2
> +++ b/man2/copy_file_range.2
> @@ -177,7 +177,7 @@ specified data types.
> .I fd_out
> refers to an immutable file.
> .TP
> -.B TXTBSY
> +.B ETXTBSY
> Either
> .I fd_in
> or
>
next prev parent reply other threads:[~2019-10-31 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 3:20 [PATCH] copy_file_range.2: tfix Yang Xu
2019-10-31 5:25 ` Michael Kerrisk (man-pages) [this message]
2019-12-09 10:56 Nikola Forró
2019-12-12 8:36 ` Michael Kerrisk (man-pages)
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=8979d26f-9abd-3592-6390-823eda85bea4@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=xuyang2018.jy@cn.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;
as well as URLs for NNTP newsgroup(s).