From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] futex.2: srcfix
Date: Fri, 30 Oct 2020 20:18:46 +0100 [thread overview]
Message-ID: <cc2918a3-5413-7f88-46b1-c73c1d24d27a@gmail.com> (raw)
In-Reply-To: <20201030123956.36169-1-colomar.6.4.3@gmail.com>
On 10/30/20 1:39 PM, Alejandro Colomar wrote:
> Signed-off-by: Alejandro Colomar <colomar.6.4.3@gmail.com>
Hi Alex,
I've applied this patch, but would prefer to avoid such
patches in the future. Nothing is actually broken in the
old version, so I tend to regard such patches as unnecessary
chur,.
Thanks,
Michael
> ---
> man2/futex.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/futex.2 b/man2/futex.2
> index f82602c11..837adbd25 100644
> --- a/man2/futex.2
> +++ b/man2/futex.2
> @@ -25,8 +25,8 @@ futex \- fast user-space locking
> .SH SYNOPSIS
> .nf
> .PP
> -.B "#include <linux/futex.h>"
> -.B "#include <sys/time.h>"
> +.B #include <linux/futex.h>
> +.B #include <sys/time.h>
> .PP
> .BI "int futex(int *" uaddr ", int " futex_op ", int " val ,
> .BI " const struct timespec *" timeout , \
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-10-30 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 12:39 Alejandro Colomar
2020-10-30 12:39 ` [PATCH 2/2] futex.2: Use appropriate types Alejandro Colomar
2020-10-30 13:46 ` Alejandro Colomar
2020-10-30 19:55 ` Michael Kerrisk (man-pages)
2020-10-30 19:19 ` Michael Kerrisk (man-pages)
2020-10-30 19:18 ` Michael Kerrisk (man-pages) [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=cc2918a3-5413-7f88-46b1-c73c1d24d27a@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=colomar.6.4.3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
/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
all inboxes | Powered by JetHome®