All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Thomas Voss <mail@tvoss.eu>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man/man2/copy_file_range.2: ffix
Date: Thu, 14 May 2026 00:22:42 +0200	[thread overview]
Message-ID: <agT5mZwAGQzlcHSe@devuan> (raw)
In-Reply-To: <b9f152d28bcff7ae45189138485e122d696defe6.1778709713.git.mail@tvoss.eu>

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

On 2026-05-14T00:01:53+0200, Thomas Voss wrote:
> Hi!

Hi Thomas!

> 
> Just came across this formatting issue in copy_file_range(2).  I went
> ahead and wrote a quick fix and also did some searching for similar bugs
> across the rest of the manuals with Awk, but didn’t come across
> anything.
> 
> — Thomas
> 
> Signed-off-by: Thomas Voss <mail@tvoss.eu>

Thanks!  I've applied the patch.


Have a lovely night!
Alex

> ---
>  man/man2/copy_file_range.2 | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/man/man2/copy_file_range.2 b/man/man2/copy_file_range.2
> index de502867d..a8ed82c4f 100644
> --- a/man/man2/copy_file_range.2
> +++ b/man/man2/copy_file_range.2
> @@ -211,7 +211,8 @@ provided a user-space fallback implementation when the kernel did not
>  implement this system call.
>  .\" glibc.git 5a659ccc0ec2 (2019-06-28; "io: Remove copy_file_range emulation [BZ #24744]")
>  Since glibc 2.30, that fallback has been removed; the function now
> -fails with ENOSYS if the kernel lacks support for .BR copy_file_range ().
> +fails with ENOSYS if the kernel lacks support for
> +.BR copy_file_range ().
>  .SH NOTES
>  If
>  .I fd_in
> -- 
> 2.54.0
> 
> 

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-05-13 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 22:01 [PATCH] man/man2/copy_file_range.2: ffix Thomas Voss
2026-05-13 22:22 ` Alejandro Colomar [this message]

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=agT5mZwAGQzlcHSe@devuan \
    --to=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mail@tvoss.eu \
    /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.