From: Paul Moore <paul@paul-moore.com>
To: Richard Haines <richard_c_haines@btinternet.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH V2 3/7] object_classes_permissions.md: Deprecate lockdown class
Date: Wed, 8 Dec 2021 15:10:37 -0500 [thread overview]
Message-ID: <CAHC9VhRH5oBMcae3HbjzvVYpTDpUWjEd1mCUWdu_yJW-TLtu3Q@mail.gmail.com> (raw)
In-Reply-To: <20211208121654.7591-4-richard_c_haines@btinternet.com>
On Wed, Dec 8, 2021 at 7:17 AM Richard Haines
<richard_c_haines@btinternet.com> wrote:
>
> Add text regarding the removal of lockdown hooks from kernel 5.16.
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
> ---
> src/object_classes_permissions.md | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
Merged, thank you.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2021-12-08 20:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 12:16 [PATCH V2 0/7] Various SELinux Notebook updates Richard Haines
2021-12-08 12:16 ` [PATCH V2 1/7] notebook: Minor formatting fixes Richard Haines
2021-12-08 20:05 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 2/7] object_classes_permissions.md: Correct the context object class entry Richard Haines
2021-12-08 20:09 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 3/7] object_classes_permissions.md: Deprecate lockdown class Richard Haines
2021-12-08 20:10 ` Paul Moore [this message]
2021-12-08 12:16 ` [PATCH V2 4/7] policy_config_files.md: Update openrc_contexts contents Richard Haines
2021-12-08 20:11 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 5/7] policy_config_files.md: Update openssh_contexts contents Richard Haines
2021-12-08 20:12 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 6/7] policy_config_files.md: Update snapperd_contexts contents Richard Haines
2021-12-08 20:13 ` Paul Moore
2021-12-08 12:16 ` [PATCH V2 7/7] title.md: Clarify example code location Richard Haines
2021-12-08 20:14 ` Paul Moore
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=CAHC9VhRH5oBMcae3HbjzvVYpTDpUWjEd1mCUWdu_yJW-TLtu3Q@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.