From: David Herrmann <dh.herrmann@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Lennart Poettering <lennart@poettering.net>,
Andy Lutomirski <luto@amacapital.net>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Hugh Dickins <hughd@google.com>,
Florian Weimer <fweimer@redhat.com>,
John Stultz <john.stultz@linaro.org>,
Carlos O'Donell <carlos@systemhalted.org>
Subject: Re: File sealing man pages for review (memfd_create(2), fcntl(2))
Date: Mon, 19 Jan 2015 15:30:10 +0100 [thread overview]
Message-ID: <CANq1E4TATDWEZDbDk85BN6kQw8ZSiZJ_eSubUaFTkhQm8URMcA@mail.gmail.com> (raw)
In-Reply-To: <54BCC153.5060804@gmail.com>
Hi
On Mon, Jan 19, 2015 at 9:33 AM, Michael Kerrisk (man-pages)
<mtk.manpages@gmail.com> wrote:
> [...]
>
> By the way, I forgot to say that I also added this error under ERRORS:
>
> [[
> .TP
> .B EINVAL
> .I cmd
> is
> .BR F_ADD_SEALS
> and
> .I arg
> includes an unrecognized sealing bit or
> the filesystem containing the inode referred to by
> .I fd
> does not support sealing.
> ]]
>
> Look okay?
I thought I already mentioned that somewhere.. eh, seems I didn't :) Looks good!
>> Both man-pages look really good. Thanks a lot!
>
> You're welcome. Thanks for the initial drafts, and this review.
> The changes will go out with the next man-pages release.
Perfect! Thanks Michael!
David
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2015-01-19 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 12:49 Michael Kerrisk (man-pages)
2015-01-18 22:28 ` David Herrmann
2015-01-19 8:33 ` Michael Kerrisk (man-pages)
2015-01-19 14:30 ` David Herrmann [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=CANq1E4TATDWEZDbDk85BN6kQw8ZSiZJ_eSubUaFTkhQm8URMcA@mail.gmail.com \
--to=dh.herrmann@gmail.com \
--cc=carlos@systemhalted.org \
--cc=fweimer@redhat.com \
--cc=hughd@google.com \
--cc=john.stultz@linaro.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=mtk.manpages@gmail.com \
/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