From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] vdso.7: repetition fix
Date: Sat, 01 Feb 2014 07:46:01 +0100 [thread overview]
Message-ID: <52EC9829.30804@gmail.com> (raw)
In-Reply-To: <1391223052-20777-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Thanks, David. Applied.
Cheers,
Michael
On 02/01/2014 03:50 AM, David Prévot wrote:
> ---
> man7/vdso.7 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man7/vdso.7 b/man7/vdso.7
> index 7251561..986cb2c 100644
> --- a/man7/vdso.7
> +++ b/man7/vdso.7
> @@ -32,7 +32,7 @@ There are some system calls the kernel provides that
> user-space code ends up using frequently,
> to the point that such calls can dominate overall performance.
> This is due both to the frequency of the call as well as the
> -context-switch overhead that results from
> +context-switch overhead that results
> from exiting user space and entering the kernel.
>
> The rest of this documentation is geared toward the curious and/or
> @@ -135,7 +135,7 @@ You will frequently find it under the architecture-specific directory:
> find arch/$ARCH/ -name '*vdso*.so*' -o -name '*gate*.so*'
>
> .SS vDSO names
> -The name of vDSO shared object varies across architectures.
> +The name of vDSO varies across architectures.
> It will often show up in things like glibc's
> .BR ldd (1)
> output.
>
--
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
prev parent reply other threads:[~2014-02-01 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 2:50 [PATCH 1/2] vdso.7: repetition fix David Prévot
[not found] ` <1391223052-20777-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-02-01 2:50 ` [PATCH 2/2] getauxval.3: wfix David Prévot
[not found] ` <1391223052-20777-2-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-02-01 6:56 ` Michael Kerrisk (man-pages)
2014-02-01 3:23 ` [PATCH 1/2] vdso.7: repetition fix Mike Frysinger
2014-02-01 6:47 ` Michael Kerrisk (man-pages)
2014-02-01 6:46 ` 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=52EC9829.30804@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=taffit-8fiUuRrzOP0dnm+yROfE0A@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).