From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Kees Cook <keescook@chromium.org>, Andy Lutomirski <luto@amacapital.net>
Cc: mtk.manpages@gmail.com, Linux API <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] seccomp.2: document seccomp syscall
Date: Sun, 02 Nov 2014 17:37:06 +0100 [thread overview]
Message-ID: <54565DB2.4040700@gmail.com> (raw)
In-Reply-To: <CAGXu5jJEn5QZPrVa4UjuT34PVuadhXqSb_d=o3W04QvZq-fMNw@mail.gmail.com>
On 09/26/2014 07:55 AM, Kees Cook wrote:
> On Thu, Sep 25, 2014 at 6:29 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>> On Thu, Sep 25, 2014 at 3:47 PM, Kees Cook <keescook@chromium.org> wrote:
>>> +.SH VERSIONS
>>> +This system call first appeared in Linux 3.16.
>>> +.\" FIXME Add glibc version
>>
>> 3.17? (And remove FIXME?)
>>
>> Otherwise I like it.
>
> Ooops, yes: 3.17. Michael do you want me to resend with that
> corrected, or do you want to handle fixing that from this version?
No need. I've fixed that.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2014-11-02 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 22:47 [PATCH 0/2] add seccomp man-page Kees Cook
2014-09-25 22:47 ` [PATCH 1/2] seccomp.2: document seccomp syscall Kees Cook
2014-09-26 1:29 ` Andy Lutomirski
2014-09-26 5:55 ` Kees Cook
2014-11-02 16:37 ` Michael Kerrisk (man-pages) [this message]
2014-11-02 16:36 ` Michael Kerrisk (man-pages)
2014-11-02 17:10 ` Michael Kerrisk (man-pages)
2014-09-25 22:47 ` [PATCH 2/2] prctl.2: document SECCOMP_MODE_FILTER vs EFAULT Kees Cook
2015-01-07 8:43 ` 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=54565DB2.4040700@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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).