From: Denys Dmytriyenko <denys@ti.com>
To: Eric Ruei <e-ruei1@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH v2 0/3] Enable SGX on k3 (AM654x)
Date: Fri, 13 Jul 2018 13:29:48 -0400 [thread overview]
Message-ID: <20180713172948.GF25410@beryl> (raw)
In-Reply-To: <1531323931-31875-1-git-send-email-e-ruei1@ti.com>
Eric,
Thanks for addressing most of my comments! This looks much better, but there
are still couple issues - please see inside.
On Wed, Jul 11, 2018 at 11:45:28AM -0400, Eric Ruei wrote:
> Enable SGX on k3 (AM654x)
>
> Eric Ruei (3):
> conf: machine: k3: enable sgx
> ti-sgx-ddk-um: add k3 (AM654x) support
> ti-sgx-ddk-km: add k3 (AM654x) support
>
> conf/machine/include/k3.inc | 4 +-
> .../powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb | 92 ++++++----------------
> .../libgles/ti-sgx-ddk-um_1.14.3699939.bb | 1 +
> ...14.3699939.bb => ti-sgx-ddk-um_1.17.4948957.bb} | 10 +--
> 4 files changed, 33 insertions(+), 74 deletions(-)
> copy recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb => recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb (2%)
> copy recipes-graphics/libgles/{ti-sgx-ddk-um_1.14.3699939.bb => ti-sgx-ddk-um_1.17.4948957.bb} (93%)
>
> --
> 1.9.1
>
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2018-07-13 17:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 15:45 [PATCH v2 0/3] Enable SGX on k3 (AM654x) Eric Ruei
2018-07-11 15:45 ` [PATCH v2 1/3] conf: machine: k3: enable sgx Eric Ruei
2018-07-11 15:45 ` [PATCH v2 2/3] ti-sgx-ddk-um: add k3 (AM654x) support Eric Ruei
2018-07-13 17:44 ` Denys Dmytriyenko
2018-07-11 15:45 ` [PATCH v2 3/3] ti-sgx-ddk-km: " Eric Ruei
2018-07-13 17:31 ` Denys Dmytriyenko
2018-07-13 18:13 ` Ruei, Eric
2018-07-13 17:29 ` Denys Dmytriyenko [this message]
2018-07-13 18:11 ` [PATCH v2 0/3] Enable SGX on k3 (AM654x) Ruei, Eric
2018-07-13 18:19 ` Denys Dmytriyenko
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=20180713172948.GF25410@beryl \
--to=denys@ti.com \
--cc=e-ruei1@ti.com \
--cc=meta-ti@yoctoproject.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.