From: Jarkko Sakkinen <jarkko@kernel.org>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [PATCH v4 08/10] KEYS: trusted: tee: use tee_shm_register_kernel_buf()
Date: Mon, 21 Feb 2022 02:52:56 +0100 [thread overview]
Message-ID: <YhLweBhnmITyErqG@kernel.org> (raw)
In-Reply-To: < <CAHUa44HkQtstCyUt_J962rzysFnOJOP+e3T2gL7nV+6V5hfa9A@mail.gmail.com>>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
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@linaro.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@linaro.org>
> > Signed-off-by: Jens Wiklander <jens.wiklander@linaro.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@kernel.org>
BR, Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: linux-kernel@vger.kernel.org, op-tee@lists.trustedfirmware.org,
Sumit Garg <sumit.garg@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>,
Rijo Thomas <Rijo-john.Thomas@amd.com>,
David Howells <dhowells@redhat.com>,
Tyler Hicks <tyhicks@linux.microsoft.com>
Subject: Re: [PATCH v4 08/10] KEYS: trusted: tee: use tee_shm_register_kernel_buf()
Date: Mon, 21 Feb 2022 02:52:56 +0100 [thread overview]
Message-ID: <YhLweBhnmITyErqG@kernel.org> (raw)
In-Reply-To: <CAHUa44HkQtstCyUt_J962rzysFnOJOP+e3T2gL7nV+6V5hfa9A@mail.gmail.com>
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@linaro.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@linaro.org>
> > Signed-off-by: Jens Wiklander <jens.wiklander@linaro.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@kernel.org>
BR, Jarkko
next parent reply other threads:[~2022-02-21 1:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] < <CAHUa44HkQtstCyUt_J962rzysFnOJOP+e3T2gL7nV+6V5hfa9A@mail.gmail.com>
2022-02-21 1:52 ` Jarkko Sakkinen [this message]
2022-02-21 1:52 ` [PATCH v4 08/10] KEYS: trusted: tee: use tee_shm_register_kernel_buf() Jarkko Sakkinen
2022-03-01 14:54 ` Jens Wiklander
2022-03-01 14:54 ` Jens Wiklander
2022-02-04 9:33 [PATCH v4 00/10] tee: shared memory updates Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 01/10] hwrng: optee-rng: use tee_shm_alloc_kernel_buf() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-09 14:12 ` Jens Wiklander
2022-02-09 14:12 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 02/10] tee: remove unused tee_shm_pool_alloc_res_mem() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 03/10] tee: add tee_shm_alloc_user_buf() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 04/10] tee: simplify shm pool handling Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 05/10] tee: replace tee_shm_alloc() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 06/10] optee: add optee_pool_op_free_helper() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 07/10] tee: add tee_shm_register_{user,kernel}_buf() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 08/10] KEYS: trusted: tee: use tee_shm_register_kernel_buf() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-09 14:08 ` Jens Wiklander
2022-02-09 14:08 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 09/10] tee: replace tee_shm_register() Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-04 9:33 ` [PATCH v4 10/10] tee: refactor TEE_SHM_* flags Jens Wiklander
2022-02-04 9:33 ` Jens Wiklander
2022-02-16 6:40 ` [PATCH v4 00/10] tee: shared memory updates Jens Wiklander
2022-02-16 6:40 ` Jens Wiklander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YhLweBhnmITyErqG@kernel.org \
--to=jarkko@kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.