From: James Morris <jmorris@namei.org>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] linux-integrity patches for Linux 5.2
Date: Sat, 13 Apr 2019 08:22:34 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1904130822070.31568@namei.org> (raw)
In-Reply-To: <1555032089.4914.4.camel@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
On Thu, 11 Apr 2019, Mimi Zohar wrote:
> Hi James,
>
> This pull request contains just three patches, the remainder are
> either included in other pull requests (eg. audit, lockdown) or will
> be upstreamed via other subsystems (eg. kselftests, Power). Included
> in this pull request is one bug fix, one documentation update, and
> extending the x86 IMA arch policy rules to coordinate the different
> kernel module signature verification methods.
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-integrity
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2019-04-12 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 1:21 [GIT PULL] linux-integrity patches for Linux 5.2 Mimi Zohar
2019-04-12 22:22 ` James Morris [this message]
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=alpine.LRH.2.21.1904130822070.31568@namei.org \
--to=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.ibm.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