[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.1905240252440.31508@namei.org>
Date: Fri, 24 May 2019 02:54:20 +1000 (AEST)
From: James Morris <jmorris@...ei.org>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
cc: Matthew Garrett <matthewgarrett@...gle.com>,
linux-integrity@...r.kernel.org, peterhuewe@....de, jgg@...pe.ca,
roberto.sassu@...wei.com, linux-efi@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, tweek@...gle.com, bsz@...ihalf.com
Subject: Re: [PATCH V7 0/4] Add support for crypto agile logs
On Thu, 23 May 2019, Jarkko Sakkinen wrote:
> On Thu, May 23, 2019 at 03:14:49PM +0300, Jarkko Sakkinen wrote:
> > On Mon, May 20, 2019 at 01:54:57PM -0700, Matthew Garrett wrote:
> > > Identical to previous version except without the KSAN workaround - Ard
> > > has a better solution for that.
> >
> >
> > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
> > Tested-by: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
>
> Only applied to my master at this point becaues the patches from
> my earlier PRs are not yet mirrored to security/next-general.
Which PRs are these?
btw, Linus wants security subsystem maintainers to submit PRs directly to
him from now on.
I'll only be carrying patches for the core LSM and new security mechanisms
before they're merged and have a maintainer assigned.
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists