[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHUa44Ex0i345f-USHJ-QovTf3ZYs0rTDufYGrtaZJNVksKqgQ@mail.gmail.com>
Date: Tue, 1 Mar 2022 15:54:20 +0100
From: Jens Wiklander <jens.wiklander@...aro.org>
To: Jarkko Sakkinen <jarkko@...nel.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 Mon, Feb 21, 2022 at 2:52 AM Jarkko Sakkinen <jarkko@...nel.org> wrote:
>
> 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
Thanks. Unfortunately it's a bit late to apply the R-B, I've already
sent the pull request to arm-soc and it has been imported into that
tree.
Thanks,
Jens
Powered by blists - more mailing lists