From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] Landlock updates for v6.1
Date: Tue, 4 Oct 2022 19:14:14 +0200 [thread overview]
Message-ID: <20221004171414.974585-1-mic@digikod.net> (raw)
Hi Linus,
This changes improve user help for Landlock (documentation and sample).
Please pull this Landlock changes for v6.1-rc1 . These 3 commits merged
cleanly with your tree, and have been successfully tested in the latest
linux-next releases.
Regards,
Mickaël
--
The following changes since commit f76349cf41451c5c42a99f18a9163377e4b364ff:
Linux 6.0-rc7 (2022-09-25 14:01:02 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-6.1-rc1
for you to fetch changes up to 2fff00c81d4c37a037cf704d2d219fbcb45aea3c:
landlock: Fix documentation style (2022-09-29 18:43:04 +0200)
----------------------------------------------------------------
Landlock updates for v6.1-rc1
----------------------------------------------------------------
Mickaël Salaün (3):
samples/landlock: Print hints about ABI versions
landlock: Slightly improve documentation and fix spelling
landlock: Fix documentation style
Documentation/security/landlock.rst | 8 +++----
Documentation/userspace-api/landlock.rst | 33 +++++++++++++-------------
include/uapi/linux/landlock.h | 10 ++++----
samples/landlock/sandboxer.c | 37 ++++++++++++++++++++++-------
security/landlock/fs.c | 2 +-
security/landlock/syscalls.c | 40 ++++++++++++++++----------------
6 files changed, 76 insertions(+), 54 deletions(-)
next reply other threads:[~2022-10-04 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 17:14 Mickaël Salaün [this message]
2022-10-04 18:18 ` pr-tracker-bot
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=20221004171414.974585-1-mic@digikod.net \
--to=mic@digikod.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®