All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Julian Orth <ju.orth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] capget.2: capset works with gettid not getpid.
Date: Fri, 12 Jun 2015 20:17:45 +0200	[thread overview]
Message-ID: <557B2249.8050509@gmail.com> (raw)
In-Reply-To: <1433966193-19774-1-git-send-email-ju.orth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Thanks, Julian. Applied.

Cheers,

Michael


On 06/10/2015 09:56 PM, Julian Orth wrote:
> ---
>  man2/capget.2 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man2/capget.2 b/man2/capget.2
> index 44ba568..014b974 100644
> --- a/man2/capget.2
> +++ b/man2/capget.2
> @@ -140,7 +140,7 @@ That is, with VFS support, for
>  calls the only permitted values for
>  .I hdrp->pid
>  are 0 or
> -.BR getpid (2),
> +.BR gettid (2),
>  which are equivalent.
>  .SS Without VFS capability support
>  When the kernel does not support VFS capabilities,
> 


-- 
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

      parent reply	other threads:[~2015-06-12 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 19:56 [PATCH] capget.2: capset works with gettid not getpid Julian Orth
     [not found] ` <1433966193-19774-1-git-send-email-ju.orth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-12 18:17   ` 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=557B2249.8050509@gmail.com \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ju.orth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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.