Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sat, 3 Nov 2018 05:15:47 +1100 (AEDT)
From:   James Morris <jmorris@namei.org>
To:     Linus Torvalds <torvalds@linux-foundation.org>
cc:     linux-security-module@vger.kernel.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-integrity@vger.kernel.org
Subject: Re: [GIT PULL] security: keys updates for v4.20
In-Reply-To: <CAHk-=wgiWxgsvmSs=BewWpfLB=vjCJ4U3yzaKzDsZVFA0L3Xtw@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1811030513480.31297@namei.org>
References: <alpine.LRH.2.21.1810262033270.5228@namei.org> <CAHk-=wgiWxgsvmSs=BewWpfLB=vjCJ4U3yzaKzDsZVFA0L3Xtw@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 1 Nov 2018, Linus Torvalds wrote:

> On Fri, Oct 26, 2018 at 2:36 AM James Morris <jmorris@namei.org> wrote:
> >
> > From David: "Provide five new operations in the key_type struct that can
> > be used to provide access to asymmetric key operations.  These will be
> > implemented for the asymmetric key type in a later patch and may refer to
> > a key retained in RAM by the kernel or a key retained in crypto hardware.
> 
> Pulled.
> 
> However. I really would have expected some of the TPM people to have
> acked these, or at least looked at them. There was no sign of that in
> any of the tpm commits that I could see..
> 
> Hmm?

Good poin.  I'll ensure the linux-integrity list (now cc'd) is always 
included when asking for review of code which touches TPM.

-- 
James Morris
<jmorris@namei.org>