[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhLweBhnmITyErqG@kernel.org>
Date: Mon, 21 Feb 2022 02:52:56 +0100
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Jens Wiklander <jens.wiklander@...aro.org>
Cc: linux-kernel@...r.kernel.org, op-tee@...ts.trustedfirmware.org,
Sumit Garg <sumit.garg@...aro.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Devaraj Rangasamy <Devaraj.Rangasamy@....com>,
Rijo Thomas <Rijo-john.Thomas@....com>,
David Howells <dhowells@...hat.com>,
Tyler Hicks <tyhicks@...ux.microsoft.com>
Subject: Re: [PATCH v4 08/10] KEYS: trusted: tee: use
tee_shm_register_kernel_buf()
On Wed, Feb 09, 2022 at 03:08:48PM +0100, Jens Wiklander wrote:
> Hi Jarkko,
>
> On Fri, Feb 4, 2022 at 10:34 AM Jens Wiklander
> <jens.wiklander@...aro.org> wrote:
> >
> > Uses the new simplified tee_shm_register_kernel_buf() function instead
> > of the old tee_shm_alloc() function which required specific
> > TEE_SHM-flags
> >
> > Reviewed-by: Sumit Garg <sumit.garg@...aro.org>
> > Signed-off-by: Jens Wiklander <jens.wiklander@...aro.org>
> > ---
> > security/keys/trusted-keys/trusted_tee.c | 23 +++++++++--------------
> > 1 file changed, 9 insertions(+), 14 deletions(-)
>
> Since this patch depends on other patches in this patch set and vice
> versa is it OK if I take this patch via my tree? I'm aiming for v5.18
> with this.
Yes.
You can also add:
Reviewed-by: Jarkko Sakkinen <jarkko@...nel.org>
BR, Jarkko
Powered by blists - more mailing lists