From: corbet@lwn.net (Jonathan Corbet)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 06/17] doc: security: minor cleanups to build kernel-doc
Date: Mon, 15 May 2017 11:21:49 -0600 [thread overview]
Message-ID: <20170515112149.2ef38651@lwn.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1705150915360.29831@namei.org>
On Mon, 15 May 2017 09:17:25 +1000 (AEST)
James Morris <jmorris@namei.org> wrote:
> On Sat, 13 May 2017, Kees Cook wrote:
>
> > These fixes were needed to parse lsm_hooks.h kernel-doc. More work is
> > needed, but this is the first step.
> >
> > Cc: Casey Schaufler <casey@schaufler-ca.com>
> > Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Should these changes go in via the docs tree or mine?
>
> In any case:
> Acked-by: James Morris <james.l.morris@oracle.com>
These changes are entirely independent from the documentation stuff, so it
could really go either way. I'm happy to carry them with the set, if that
works for you.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: James Morris <jmorris@namei.org>
Cc: Kees Cook <keescook@chromium.org>,
Casey Schaufler <casey@schaufler-ca.com>,
John Johansen <john.johansen@canonical.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Paul Moore <paul@paul-moore.com>,
David Howells <dhowells@redhat.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
James Morris <james.l.morris@oracle.com>,
Tyler Hicks <tyhicks@canonical.com>,
David Safford <safford@us.ibm.com>,
linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 06/17] doc: security: minor cleanups to build kernel-doc
Date: Mon, 15 May 2017 11:21:49 -0600 [thread overview]
Message-ID: <20170515112149.2ef38651@lwn.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1705150915360.29831@namei.org>
On Mon, 15 May 2017 09:17:25 +1000 (AEST)
James Morris <jmorris@namei.org> wrote:
> On Sat, 13 May 2017, Kees Cook wrote:
>
> > These fixes were needed to parse lsm_hooks.h kernel-doc. More work is
> > needed, but this is the first step.
> >
> > Cc: Casey Schaufler <casey@schaufler-ca.com>
> > Signed-off-by: Kees Cook <keescook@chromium.org>
>
> Should these changes go in via the docs tree or mine?
>
> In any case:
> Acked-by: James Morris <james.l.morris@oracle.com>
These changes are entirely independent from the documentation stuff, so it
could really go either way. I'm happy to carry them with the set, if that
works for you.
Thanks,
jon
next prev parent reply other threads:[~2017-05-15 17:21 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 11:51 [PATCH 00/17] convert/reorganize Documentation/security/ Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 01/17] doc: ReSTify seccomp_filter.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 02/17] doc: ReSTify no_new_privs.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 03/17] doc: ReSTify IMA-templates.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 04/17] doc: ReSTify credentials.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 05/17] doc: ReSTify self-protection.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 06/17] doc: security: minor cleanups to build kernel-doc Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-14 23:17 ` James Morris
2017-05-14 23:17 ` James Morris
2017-05-15 17:21 ` Jonathan Corbet [this message]
2017-05-15 17:21 ` Jonathan Corbet
2017-05-15 0:00 ` Casey Schaufler
2017-05-15 0:00 ` Casey Schaufler
2017-05-15 14:42 ` Kees Cook
2017-05-15 14:42 ` Kees Cook
2017-05-13 11:51 ` [PATCH 07/17] doc: ReSTify and split LSM.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 08/17] doc: ReSTify SELinux.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-17 20:08 ` Paul Moore
2017-05-17 20:08 ` Paul Moore
2017-05-13 11:51 ` [PATCH 09/17] doc: ReSTify apparmor.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 19:47 ` John Johansen
2017-05-13 19:47 ` John Johansen
2017-05-13 11:51 ` [PATCH 10/17] doc: ReSTify tomoyo.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-14 6:51 ` Tetsuo Handa
2017-05-13 11:51 ` [PATCH 11/17] doc: ReSTify Yama.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 12/17] doc: ReSTify LoadPin.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 13/17] doc: ReSTify Smack.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-15 14:13 ` Casey Schaufler
2017-05-15 14:13 ` Casey Schaufler
2017-05-13 11:51 ` [PATCH 14/17] doc: ReSTify keys.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 15/17] doc: ReSTify keys-ecryptfs.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 16/17] doc: ReSTify keys-request-key.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-13 11:51 ` [PATCH 17/17] doc: ReSTify keys-trusted-encrypted.txt Kees Cook
2017-05-13 11:51 ` Kees Cook
2017-05-15 17:26 ` [PATCH 00/17] convert/reorganize Documentation/security/ Jonathan Corbet
2017-05-15 17:26 ` Jonathan Corbet
2017-05-15 17:33 ` Kees Cook
2017-05-15 17:33 ` Kees Cook
2017-05-18 16:49 ` Jonathan Corbet
2017-05-18 16:49 ` Jonathan Corbet
2017-05-18 17:01 ` Kees Cook
2017-05-18 17:01 ` Kees Cook
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=20170515112149.2ef38651@lwn.net \
--to=corbet@lwn.net \
--cc=linux-security-module@vger.kernel.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.