From: Alejandro Colomar <alx@kernel.org>
To: "Günther Noack" <gnoack3000@gmail.com>
Cc: "Mickaël Salaün" <mic@digikod.net>, linux-man@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Update Landlock docs to Landlock ABI v8
Date: Wed, 22 Apr 2026 21:32:29 +0200 [thread overview]
Message-ID: <aekh8O3sOyudHw44@devuan> (raw)
In-Reply-To: <20260422192330.7623-1-gnoack3000@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]
On 2026-04-22T21:23:28+0200, Günther Noack wrote:
> Hello!
Hello!
> Thanks for the review! Here's the fourth round of the patch set, this
> time just adding the missing ABI version information. Added another
> small patch in the same style for the adjacent Landlock man page where
> it applies. (The third Landlock manpage, landlock_create_ruleset.2,
> doesn't need it because one flag is available since the start and the
> errata flag is available where needed and backported everywhere, as
> previously discussed.)
Thanks!
> Kept the cover letter title as is, to reduce confusion (but the part
> where Landlock ABI v8 gets described is already submitted).
You may want to use --in-reply-to instead, so that all revisions are
subthreads of the same thread (v1). But thanks!
>
> –Günther
>
> P.S.: I have a half-finished commit for the upcoming Linux 7.1 release
> as well; I can send this one soon, I assume it's OK to send these
> slightly before the release, given that the code is already on Linux
> master?
Yup, that's fine.
Have a lovely night!
Alex
>
>
> Change Log
> ==========
>
> v4:
> - mention ABI versions for flags next to the tagged paragraph title
> where they are described
> - 1/2: do that in landlock_restrict_self.2 (based on v3's patch 4)
> - 2/2: do that in landlock_add_rule.2 as well
> - earlier patches 1,2,3 from v3 were already merged
>
> v3:
> - split the size/attr clarifications from the "errata" patch into a
> separate commit
> - earlier patch from v2 about the "scoped" EINVAL error was already
> merged
>
> v2:
> - landlock_create_ruleset.2: added a tiny patch to add a missing
> mention of "scoped" in the errors list.
> - landlock_create_ruleset.2: various reformulations for errata
> - earlier patch from v1 about the default ABI version assumption was
> already merged (thanks!)
>
> Günther Noack (2):
> man/man2/landlock_restrict_self.2: Document ABI requirement for
> logging flags
> man/man2/landlock_add_rule.2: mention ABI version for
> LANDLOCK_RULE_NET_PORT
>
> man/man2/landlock_add_rule.2 | 2 +-
> man/man2/landlock_restrict_self.2 | 6 +++---
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.53.0
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-04-22 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 19:23 [PATCH v4 0/2] Update Landlock docs to Landlock ABI v8 Günther Noack
2026-04-22 19:23 ` [PATCH v4 1/2] man/man2/landlock_restrict_self.2: Document ABI requirement for logging flags Günther Noack
2026-04-22 19:23 ` [PATCH v4 2/2] man/man2/landlock_add_rule.2: mention ABI version for LANDLOCK_RULE_NET_PORT Günther Noack
2026-04-22 19:32 ` Alejandro Colomar [this message]
2026-05-04 13:03 ` [PATCH v4 0/2] Update Landlock docs to Landlock ABI v8 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=aekh8O3sOyudHw44@devuan \
--to=alx@kernel.org \
--cc=gnoack3000@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mic@digikod.net \
/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