[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190813130702.GC9079@rotor.kitware.com>
Date: Tue, 13 Aug 2019 09:07:02 -0400
From: Ben Boeckel <mathstuf@...il.com>
To: Alison Schofield <alison.schofield@...el.com>
Cc: "Kirill A. Shutemov" <kirill@...temov.name>,
Andrew Morton <akpm@...ux-foundation.org>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...capital.net>,
David Howells <dhowells@...hat.com>,
Kees Cook <keescook@...omium.org>,
Dave Hansen <dave.hansen@...el.com>,
Kai Huang <kai.huang@...ux.intel.com>,
Jacob Pan <jacob.jun.pan@...ux.intel.com>, linux-mm@...ck.org,
kvm@...r.kernel.org, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCHv2 57/59] x86/mktme: Document the MKTME Key Service API
On Mon, Aug 05, 2019 at 13:44:53 -0700, Alison Schofield wrote:
> Yes. Fixed up as follows:
>
> Add a "no-encrypt' type key::
>
> char \*options_NOENCRYPT = "type=no-encrypt";
>
> key = add_key("mktme", "name", options_NOENCRYPT,
> strlen(options_NOENCRYPT), KEY_SPEC_THREAD_KEYRING);
Thanks. Looks good to me.
Reviewed-by: Ben Boeckel <mathstuf@...il.com>
--Ben
Powered by blists - more mailing lists