From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: efremov <efremov@ispras.ru>, James Morris <jmorris@namei.org>,
linux-doc@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] doc: security: Add kern-doc for lsm_hooks.h
Date: Fri, 22 Feb 2019 08:55:27 -0700 [thread overview]
Message-ID: <20190222085527.17eabf78@lwn.net> (raw)
In-Reply-To: <20190217221901.GA41920@beast>
On Sun, 17 Feb 2019 14:19:01 -0800
Kees Cook <keescook@chromium.org> wrote:
> There is a lot of kern-doc for the LSM internals, but it wasn't visible
> in the HTML output. This exposes some formatting flaws in lsm_hooks.h
> that will be fixed in a later series of patches.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
Applied, thanks. That does add to our already overwhelming pile of
warnings, hopefully that later series is showing up soon :)
jon
prev parent reply other threads:[~2019-02-22 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 22:19 [PATCH] doc: security: Add kern-doc for lsm_hooks.h Kees Cook
2019-02-22 15:55 ` Jonathan Corbet [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=20190222085527.17eabf78@lwn.net \
--to=corbet@lwn.net \
--cc=efremov@ispras.ru \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).