From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] syscall.2: srcfix
Date: Sun, 22 Mar 2015 19:53:23 +0100 [thread overview]
Message-ID: <550F0FA3.1000108@gmail.com> (raw)
In-Reply-To: <1426385789-12406-2-git-send-email-saulery-GANU6spQydw@public.gmane.org>
On 03/15/2015 03:16 AM, Stéphane Aulery wrote:
> Fix a warning of groff: line 192: warning [p 2, 4.7i]: cannot adjust line
Thanks, Stéphane. Applied.
Cheers,
Michael
> Signed-off-by: Stéphane Aulery <saulery-GANU6spQydw@public.gmane.org>
> ---
> man2/syscall.2 | 32 ++++++++++++++++----------------
> 1 file changed, 16 insertions(+), 16 deletions(-)
>
> diff --git a/man2/syscall.2 b/man2/syscall.2
> index ad2e05e..ef8f3cf 100644
> --- a/man2/syscall.2
> +++ b/man2/syscall.2
> @@ -193,23 +193,23 @@ The second table shows the registers used to pass the system call arguments.
> .ft CW
> \}
> .TS
> -l l2 l2 l2 l2 l2 l2 l2 l.
> -arch/ABI arg1 arg2 arg3 arg4 arg5 arg6 arg7 Notes
> +l l2 l2 l2 l2 l2 l2 l2 l.
> +arch/ABI arg1 arg2 arg3 arg4 arg5 arg6 arg7 Notes
> _
> -arm/OABI a1 a2 a3 a4 v1 v2 v3
> -arm/EABI r0 r1 r2 r3 r4 r5 r6
> -arm64 x0 x1 x2 x3 x4 x5 -
> -blackfin R0 R1 R2 R3 R4 R5 -
> -i386 ebx ecx edx esi edi ebp -
> -ia64 out0 out1 out2 out3 out4 out5 -
> -mips/o32 a0 a1 a2 a3 - - - See below
> -mips/n32,64 a0 a1 a2 a3 a4 a5 -
> -parisc r26 r25 r24 r23 r22 r21 -
> -s390 r2 r3 r4 r5 r6 r7 -
> -s390x r2 r3 r4 r5 r6 r7 -
> -sparc/32 o0 o1 o2 o3 o4 o5 -
> -sparc/64 o0 o1 o2 o3 o4 o5 -
> -x86_64 rdi rsi rdx r10 r8 r9 -
> +arm/OABI a1 a2 a3 a4 v1 v2 v3
> +arm/EABI r0 r1 r2 r3 r4 r5 r6
> +arm64 x0 x1 x2 x3 x4 x5 -
> +blackfin R0 R1 R2 R3 R4 R5 -
> +i386 ebx ecx edx esi edi ebp -
> +ia64 out0 out1 out2 out3 out4 out5 -
> +mips/o32 a0 a1 a2 a3 - - - See below
> +mips/n32,64 a0 a1 a2 a3 a4 a5 -
> +parisc r26 r25 r24 r23 r22 r21 -
> +s390 r2 r3 r4 r5 r6 r7 -
> +s390x r2 r3 r4 r5 r6 r7 -
> +sparc/32 o0 o1 o2 o3 o4 o5 -
> +sparc/64 o0 o1 o2 o3 o4 o5 -
> +x86_64 rdi rsi rdx r10 r8 r9 -
> .TE
> .PP
> The mips/o32 system call convention passes
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-22 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 2:16 [PATCH 1/2] ioctl_list.2: srcfix Stéphane Aulery
[not found] ` <1426385789-12406-1-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-15 2:16 ` [PATCH 2/2] syscall.2: srcfix Stéphane Aulery
[not found] ` <1426385789-12406-2-git-send-email-saulery-GANU6spQydw@public.gmane.org>
2015-03-22 18:53 ` Michael Kerrisk (man-pages) [this message]
2015-03-22 18:53 ` [PATCH 1/2] ioctl_list.2: srcfix 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=550F0FA3.1000108@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=saulery-GANU6spQydw@public.gmane.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;
as well as URLs for NNTP newsgroup(s).