From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] lsm/lsm-pr-20240513
Date: Mon, 13 May 2024 15:47:12 -0400 [thread overview]
Message-ID: <eb9e94532b792619e4161de6c0a397db@paul-moore.com> (raw)
Linus,
Three fairly minor patches for the current merge window; highlights
below:
- The security/* portion of the effort to remove the empty sentinel
elements at the end of the ctl_table arrays.
- Update the file list associated with the LSM / "SECURITY SUBSYSTEM"
entry in the MAINTAINERS file (and then fix a typo in then update).
Please merge for Linux v6.10.
-Paul
--
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
tags/lsm-pr-20240513
for you to fetch changes up to dd80c7465029dd0671e6f9fc2678ae0fbdf785ac:
MAINTAINERS: repair file entry in SECURITY SUBSYSTEM
(2024-05-07 10:56:15 -0400)
----------------------------------------------------------------
lsm/stable-6.10 PR 20240513
----------------------------------------------------------------
Joel Granados (1):
lsm: remove the now superfluous sentinel element from ctl_table array
Lukas Bulwahn (1):
MAINTAINERS: repair file entry in SECURITY SUBSYSTEM
Paul Moore (1):
MAINTAINERS: update the LSM file list
MAINTAINERS | 4 ++++
security/apparmor/lsm.c | 1 -
security/keys/sysctl.c | 1 -
security/loadpin/loadpin.c | 1 -
security/yama/yama_lsm.c | 1 -
5 files changed, 4 insertions(+), 4 deletions(-)
--
paul-moore.com
next reply other threads:[~2024-05-13 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 19:47 Paul Moore [this message]
2024-05-15 16:35 ` [GIT PULL] lsm/lsm-pr-20240513 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=eb9e94532b792619e4161de6c0a397db@paul-moore.com \
--to=paul@paul-moore.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).