[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171011115254.2n4zs77ixyl2mdgm@linux.intel.com>
Date: Wed, 11 Oct 2017 14:52:54 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: James Morris <jmorris@...ei.org>
Cc: Thiebaud Weksteen <tweek@...gle.com>, linux-efi@...r.kernel.org,
linux-integrity@...r.kernel.org, tpmdd-devel@...ts.sourceforge.net,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Matt Fleming <matt@...eblueprint.co.uk>,
linux-kernel@...r.kernel.org, Matthew Garrett <mjg59@...gle.com>,
peterhuewe@....de,
Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
tpmdd@...horst.net
Subject: Re: [PATCH v3 4/5] efi: call get_event_log before ExitBootServices
On Wed, Oct 11, 2017 at 12:54:26PM +1100, James Morris wrote:
> On Tue, 10 Oct 2017, Jarkko Sakkinen wrote:
>
> > The way I've agreed with James Morris to have my tree is to be rooted to
> > security trees next branch.
> >
> > James, what actions should we take?
>
> This process has changed recently -- I posted to lsm but forgot to post to
> linux-integrity.
>
> http://kernsec.org/pipermail/linux-security-module-archive/2017-September/003356.html
>
> Summary: please track the next-general branch in my tree for your
> development, it replaces 'next'.
>
>
> - James
> --
> James Morris
> <jmorris@...ei.org>
Ah I'm subscribed to that list but lately been busy getting a huge patch
set to platform-driver-x86 [1] for review, which has prioritized out
reading much else than linux-integrity.
Thank you. I'll retry the patches tomorrow.
/Jarkko
Powered by blists - more mailing lists