From: "Günther Noack" <gnoack3000@gmail.com>
To: "Alejandro Colomar" <alx.manpages@gmail.com>,
"Mickaël Salaün" <mic@digikod.net>
Cc: "Michael Kerrisk" <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org, "Günther Noack" <gnoack3000@gmail.com>
Subject: [PATCH v6 0/1] landlock.7: Explain best-effort fallback in example
Date: Fri, 14 Apr 2023 17:59:25 +0200 [thread overview]
Message-ID: <20230414155926.6937-1-gnoack3000@gmail.com> (raw)
Hello!
Same patch as before, but the first two commits are already merged. :)
The only addition is a little remark in the example code to point out
that these values are hardcoded for brevity.
In the long run I would like to put these constants in a kernel uapi
header. In the meanwhile, I think it's good to point it out
explicitly in the man page that this is just done like that to keep
the example short.
–Günther
Günther Noack (1):
landlock.7: Explain the best-effort fallback mechanism in the example
man7/landlock.7 | 70 ++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 66 insertions(+), 4 deletions(-)
base-commit: 6e502b913302d5ba4b70a2f3e6b3ff38748d2d0f
--
2.40.0
next reply other threads:[~2023-04-14 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 15:59 Günther Noack [this message]
2023-04-14 15:59 ` [PATCH v6 1/1] landlock.7: Explain the best-effort fallback mechanism in the example Günther Noack
2023-04-14 16:35 ` Alejandro Colomar
2023-04-15 7:16 ` Günther Noack
2023-04-17 17:24 ` Alejandro Colomar
2023-04-17 20:54 ` Mickaël Salaün
2023-04-18 14:37 ` Alejandro Colomar
2023-04-18 20:50 ` Mickaël Salaün
2023-04-18 20:54 ` Alejandro Colomar
2023-04-18 20:55 ` Alejandro Colomar
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=20230414155926.6937-1-gnoack3000@gmail.com \
--to=gnoack3000@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mic@digikod.net \
--cc=mtk.manpages@gmail.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).