From: James Morris <jmorris@namei.org>
To: Denis Efremov <efremov@ispras.ru>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Kees Cook <keescook@chromium.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Eric Paris <eparis@parisplace.org>,
John Johansen <john.johansen@canonical.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
Paul Moore <paul@paul-moore.com>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/11] LSM documentation update
Date: Wed, 27 Mar 2019 13:22:23 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1903271322120.9951@namei.org> (raw)
In-Reply-To: <cover.1551213058.git.efremov@ispras.ru>
On Tue, 26 Feb 2019, Denis Efremov wrote:
> Recent "New LSM Hooks" discussion has led me to the
> thought that it might be a good idea to slightly
> update the current documentation. The patchset adds
> nothing new to the documentation, only fixes the old
> description of hooks to reflect their current state.
>
> V2 adds the clarification on arguments for some hooks.
> The format of the documentation is also slightly updated
> for better html. However, there are still 10 hooks without
> documentation at all. I think that this should be fixed
> separatedly.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
Thanks!
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2019-03-27 2:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 20:49 Denis Efremov
2019-02-26 20:49 ` [PATCH v2 01/11] LSM: fix documentation for sb_copy_data hook Denis Efremov
2019-02-26 20:49 ` [PATCH v2 02/11] LSM: fix documentation for the syslog hook Denis Efremov
2019-02-26 20:49 ` [PATCH v2 03/11] LSM: fix documentation for the socket_post_create hook Denis Efremov
2019-02-26 20:49 ` [PATCH v2 04/11] LSM: fix documentation for the task_setscheduler hook Denis Efremov
2019-02-26 20:49 ` [PATCH v2 05/11] LSM: fix documentation for the socket_getpeersec_dgram hook Denis Efremov
2019-02-26 20:49 ` [PATCH v2 06/11] LSM: fix documentation for the path_chmod hook Denis Efremov
2019-02-26 20:49 ` [PATCH v2 07/11] LSM: fix documentation for the audit_* hooks Denis Efremov
2019-02-26 20:49 ` [PATCH v2 08/11] LSM: fix documentation for the msg_queue_* hooks Denis Efremov
2019-02-26 20:49 ` [PATCH v2 09/11] LSM: fix documentation for the sem_* hooks Denis Efremov
2019-02-26 20:49 ` [PATCH v2 10/11] LSM: fix documentation for the shm_* hooks Denis Efremov
2019-02-26 20:49 ` [PATCH v2 11/11] LSM: lsm_hooks.h: fix documentation format Denis Efremov
2019-02-26 23:34 ` [PATCH v2 00/11] LSM documentation update Casey Schaufler
2019-02-27 0:09 ` Kees Cook
2019-02-27 15:10 ` Denis Efremov
2019-02-27 16:27 ` Kees Cook
2019-03-26 14:38 ` Denis Efremov
2019-03-26 14:53 ` Jonathan Corbet
2019-03-26 18:16 ` James Morris
2019-03-27 2:22 ` James Morris [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=alpine.LRH.2.21.1903271322120.9951@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=ebiederm@xmission.com \
--cc=efremov@ispras.ru \
--cc=eparis@parisplace.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=takedakn@nttdata.co.jp \
/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
all inboxes | Powered by JetHome®