All of lore.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Seonghun Lim <wariua-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] clock_getres.2: ffix
Date: Wed, 8 Nov 2017 06:58:29 -0500	[thread overview]
Message-ID: <20171108115827.rachl42whbklzlpi@crack.deadbeast.net> (raw)
In-Reply-To: <55b5b761-3b19-6578-a83d-a2a9f7452459-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

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

At 2017-11-08T16:25:04+0900, Seonghun Lim wrote:
> --- a/man2/clock_getres.2
> +++ b/man2/clock_getres.2
> @@ -275,7 +275,7 @@ If the CPUs in an SMP system have different clock sources, then
>  there is no way to maintain a correlation between the timer registers since
>  each CPU will run at a slightly different frequency.
>  If that is the case, then
> -.I clock_getcpuclockid(0)
> +.BR clock_getcpuclockid(3)

That's not a man page cross reference, it's an example of a function
call.

Even if it were a man page cross reference, you would need a space
between "clock_getcpuclockid" and "(3)".

-- 
Regards,
Branden

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

  parent reply	other threads:[~2017-11-08 11:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08  7:25 [patch] clock_getres.2: ffix Seonghun Lim
     [not found] ` <55b5b761-3b19-6578-a83d-a2a9f7452459-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-11-08 11:58   ` G. Branden Robinson [this message]
     [not found]     ` <20171108115827.rachl42whbklzlpi-Z0uaYDh/Ni4SozaZsD9aTtHuzzzSOjJt@public.gmane.org>
2017-11-09  7:55       ` Michael Kerrisk (man-pages)
  -- strict thread matches above, loose matches on Subject: below --
2012-05-05 20:33 [PATCH] " Simon Paillard
     [not found] ` <1336250035-15232-1-git-send-email-spaillard-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-05 21:37   ` 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=20171108115827.rachl42whbklzlpi@crack.deadbeast.net \
    --to=g.branden.robinson-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=wariua-Re5JQEeQqe8AvxtiuMwx3w@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 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.