From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "James Morris" <jmorris@namei.org>,
"Paul Moore" <paul@paul-moore.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
"Alejandro Colomar" <alx.manpages@gmail.com>,
"Günther Noack" <gnoack3000@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Konstantin Meskhidze" <konstantin.meskhidze@huawei.com>,
linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH v1 3/3] landlock: Fix documentation style
Date: Sat, 24 Sep 2022 16:50:11 +0700 [thread overview]
Message-ID: <Yy7S07GpqZEY4J8n@debian.me> (raw)
In-Reply-To: <20220923154207.3311629-4-mic@digikod.net>
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On Fri, Sep 23, 2022 at 05:42:07PM +0200, Mickaël Salaün wrote:
> It seems that all code should use double backquotes, which is also used
> to convert "%" defines. Let's use an homogeneous style and remove all
> use of simple backquotes (which should only be used for emphasis).
>
A little nit: the kernel log content at the opening paragraph should
also be in inline code:
---- >8 ----
diff --git a/Documentation/userspace-api/landlock.rst b/Documentation/userspace-api/landlock.rst
index cec780c2f4973c..5dbd577b5f58b7 100644
--- a/Documentation/userspace-api/landlock.rst
+++ b/Documentation/userspace-api/landlock.rst
@@ -19,10 +19,10 @@ unexpected/malicious behaviors in user space applications. Landlock empowers
any process, including unprivileged ones, to securely restrict themselves.
We can quickly make sure that Landlock is enabled in the running system by
-looking for "landlock: Up and running" in kernel logs (as root): ``dmesg | grep
-landlock || journalctl -kg landlock`` . Developers can also easily check for
-Landlock support with a :ref:`related system call <landlock_abi_versions>`. If
-Landlock is not currently supported, we need to :ref:`configure the kernel
+looking for ``landlock: Up and running`` in kernel logs (as root): ``dmesg |
+grep landlock || journalctl -kg landlock`` . Developers can also easily check
+for Landlock support with a :ref:`related system call <landlock_abi_versions>`.
+If Landlock is not currently supported, we need to :ref:`configure the kernel
appropriately <kernel_support>`.
Landlock rules
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-09-24 9:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:42 [PATCH v1 0/3] Improve Landlock help Mickaël Salaün
2022-09-23 15:42 ` [PATCH v1 1/3] samples/landlock: Print hints about ABI versions Mickaël Salaün
2022-09-23 21:02 ` Günther Noack
2022-09-27 16:23 ` Mickaël Salaün
2022-09-23 15:42 ` [PATCH v1 2/3] landlock: Slightly improve documentation and fix spelling Mickaël Salaün
2022-09-23 21:03 ` Günther Noack
2022-09-24 13:29 ` Bagas Sanjaya
2022-09-26 1:09 ` Akira Yokosawa
2022-09-26 1:46 ` Bagas Sanjaya
2022-09-26 4:10 ` Akira Yokosawa
2022-09-26 7:20 ` Bagas Sanjaya
2022-09-27 16:43 ` Mickaël Salaün
2022-09-23 15:42 ` [PATCH v1 3/3] landlock: Fix documentation style Mickaël Salaün
2022-09-23 21:18 ` Günther Noack
2022-09-27 16:58 ` Mickaël Salaün
2022-09-24 9:50 ` Bagas Sanjaya [this message]
2022-09-27 16:52 ` Mickaël Salaün
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=Yy7S07GpqZEY4J8n@debian.me \
--to=bagasdotme@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=corbet@lwn.net \
--cc=gnoack3000@gmail.com \
--cc=jmorris@namei.org \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--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).