From: Paul Moore <paul@paul-moore.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Security Module <linux-security-module@vger.kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Jarkko Sakkinen" <jarkko@kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
"Bagas Sanjaya" <bagasdotme@gmail.com>,
"Jeff Layton" <jlayton@kernel.org>, "Kees Cook" <kees@kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Stuart Yoder" <stuart.yoder@arm.com>
Subject: Re: [PATCH] security: sctp: Format type and permission checks tables
Date: Wed, 19 Nov 2025 19:10:31 -0500 [thread overview]
Message-ID: <d5efca7df0d2e12ad9d6f3d35afa2828@paul-moore.com> (raw)
In-Reply-To: <20251103113922.61232-2-bagasdotme@gmail.com>
On Nov 3, 2025 Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> Use reST grid tables for both type and permission checks tables.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> This patch is based on lsm tree.
>
> Documentation/security/SCTP.rst | 48 +++++++++++++++++++++------------
> 1 file changed, 31 insertions(+), 17 deletions(-)
I rendered the patched file to HTML, and given that large portions of
the file are still rendered as monospaced preformatted text, the new
table rendering looks a bit out of place.
Let's stick with the existing table format until the entire document
is converted to something that is at least as constitent and
aesthetically pleasing as the current revision.
--
paul-moore.com
next prev parent reply other threads:[~2025-11-20 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 11:39 [PATCH] security: sctp: Format type and permission checks tables Bagas Sanjaya
2025-11-11 2:34 ` Bagas Sanjaya
2025-11-12 0:50 ` Paul Moore
2025-11-12 12:07 ` Bagas Sanjaya
2025-11-20 0:10 ` Paul Moore [this message]
2025-11-20 1:39 ` Bagas Sanjaya
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=d5efca7df0d2e12ad9d6f3d35afa2828@paul-moore.com \
--to=paul@paul-moore.com \
--cc=bagasdotme@gmail.com \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=jarkko@kernel.org \
--cc=jlayton@kernel.org \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=stuart.yoder@arm.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).