[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.1905250506320.7233@namei.org>
Date: Sat, 25 May 2019 05:22:34 +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,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH V7 0/4] Add support for crypto agile logs
On Fri, 24 May 2019, Jarkko Sakkinen wrote:
> I'm referring to these:
>
> https://lore.kernel.org/linux-integrity/20190329115544.GA27351@linux.intel.com/
>
> I got response from you that those were applied and there is another
> response in that thread that they are being sent to Linus. That is why I
> haven't done anything since. Most of them are critical fixes to v5.1
> changes.
These are in Linus' tree.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a556810d8e06aa2da8bbe22da3d105eb5a0d0c7d
I initially queued them in the next-tpm branch, but forgot to drop them
from there after sending them to Linus as a v5.1 fix. Linus was not happy
to see them again in the v5.2 merge window.
Apologies for the confusion.
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists