From: Richard Haines <richard_c_haines@btinternet.com>
To: "Serge E. Hallyn" <serge@hallyn.com>, Paul Moore <paul@paul-moore.com>
Cc: linux-security-module@vger.kernel.org, linux-doc@vger.kernel.org,
corbet@lwn.net, James Morris <jmorris@namei.org>,
casey@schaufler-ca.com
Subject: Re: [RFC PATCH 0/3] LSM Documentation - Render lsm_hooks.h for kernel_docs
Date: Thu, 15 Apr 2021 14:53:55 +0100 [thread overview]
Message-ID: <96941e4977f38dea58a56fe19cfeb84179f0e3ef.camel@btinternet.com> (raw)
In-Reply-To: <20210413190150.GB26626@mail.hallyn.com>
On Tue, 2021-04-13 at 14:01 -0500, Serge E. Hallyn wrote:
> On Wed, Apr 07, 2021 at 09:42:01PM -0400, Paul Moore wrote:
> > On Tue, Mar 9, 2021 at 9:40 AM Richard Haines
> > <richard_c_haines@btinternet.com> wrote:
> > >
> > > This patch series updates the LSM hook text defined in the
> > > comments
> > > section of inlcude/linux/lsm_hooks.h. This enables the hook
> > > functions to
> > > be rendered in kernel_docs html or pdf format.
> > >
> > > Note that no text has been changed in lsm_hooks.h, only
> > > formatting
> > > to render the text.
> > >
> > > To get the correct rendering some lines have exceeded checkpatch
> > > limits and
> > > therefore has a moan. The function statements seem to need being
> > > a
> > > continuous line. The others can be split, but decided not to.
> > > Any better ideas ??
> > >
> > > The hook functions render in HTML ok, however in PDF format the
> > > only issue
> > > is that the long function definitions do not wrap and therefore
> > > truncated.
> > > Check the 'int sb_mount(const char *dev_name' entry in:
> > > Documentation/output/pdf/security.pdf
> > >
> > > For reference two hooks have been marked as deprecated:
> > > sb_copy_data() and
> > > sb_parse_opts_str()
> > >
> > > Tested using 'make pdfdocs' and 'make htmldocs'
> > >
> > > Richard Haines (3):
> > > Documentation/security: Update LSM security hook text
> > > include/linux: Update LSM hook text part1
> > > include/linux: Update LSM hook text part2
> > >
> > > Documentation/security/lsm-development.rst | 5 +-
> > > include/linux/lsm_hooks.h | 2365 +++++++++++---
> > > ------
> > > 2 files changed, 1364 insertions(+), 1006 deletions(-)
> >
> > I haven't yet pulled this patchset to generate the HTML/PDF docs,
> > but
> > just looking at the comments themselves it looks reasonable to me
> > ...
> > and I say this as being perhaps one of the stricter folks under
> > security/ when it comes to 80 character line lengths :) In my
> > opinion, the benefit of being able to render the docs nicely
> > outweigh
> > the pain of scrolling horizontally in my editor. Thanks for doing
> > this Richard.
> >
> > Does anyone else have any thoughts on these changes?
>
> No objection from me.
Thanks for the comments, I'll rebuild on 5.12-rc7 and resubmit as a
patch.
next prev parent reply other threads:[~2021-04-15 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 14:39 [RFC PATCH 0/3] LSM Documentation - Render lsm_hooks.h for kernel_docs Richard Haines
2021-03-09 14:39 ` [RFC PATCH 1/3] Documentation/security: Update LSM security hook text Richard Haines
2021-03-09 14:39 ` [RFC PATCH 2/3] include/linux: Update LSM hook text part1 Richard Haines
2021-03-09 14:39 ` [RFC PATCH 3/3] include/linux: Update LSM hook text part2 Richard Haines
2021-04-08 1:42 ` [RFC PATCH 0/3] LSM Documentation - Render lsm_hooks.h for kernel_docs Paul Moore
2021-04-13 19:01 ` Serge E. Hallyn
2021-04-15 13:53 ` Richard Haines [this message]
2021-04-15 13:59 ` Paul Moore
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=96941e4977f38dea58a56fe19cfeb84179f0e3ef.camel@btinternet.com \
--to=richard_c_haines@btinternet.com \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=jmorris@namei.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).