All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Ruei, Eric" <e-ruei1@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [rocko/master][PATCH v3] ti-sgx-ddk-km: update SGX kernel	driver for k4.14
Date: Tue, 3 Apr 2018 17:00:48 -0400	[thread overview]
Message-ID: <20180403210048.GF31973@edge> (raw)
In-Reply-To: <ed137a3d-d432-41d9-ac41-1a493ba8f7a1@email.android.com>

Eric,

ping


On Thu, Mar 15, 2018 at 12:59:41AM +0000, Dmytriyenko, Denys wrote:
> Absolutely
> 
> 
> 
> On Mar 14, 2018 17:58, "Ruei, Eric" <e-ruei1@ti.com> wrote:
> Hi, Denys:
> 
> I see that the v2 is in.
> Should I submit this one on top of v2 as a new patch?
> 
> Best regards,
> 
> Eric
> 
> 
> From: Dmytriyenko, Denys
> Sent: Wednesday, March 14, 2018 8:51 PM
> To: Ruei, Eric
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [rocko/master][PATCH v3] ti-sgx-ddk-km: update SGX kernel driver for k4.14
> 
> It's already in rocko/master - no rebases
> 
> 
> 
> On Mar 14, 2018 17:46, "Ruei, Eric" <e-ruei1@ti.com<mailto:e-ruei1@ti.com>> wrote:
> From: Anand Balagopalakrishnan <anandb@ti.com<mailto:anandb@ti.com>>
> 
> Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com<mailto:anandb@ti.com>>
> Signed-off-by: Eric Ruei <e-ruei1@ti.com<mailto:e-ruei1@ti.com>>
> ---
>  recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb
> index 0303797..55f6b9b 100644
> --- a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb
> +++ b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.14.3699939.bb
> @@ -20,7 +20,7 @@ RPROVIDES_${PN} = "omapdrm-pvr"
>  RREPLACES_${PN} = "omapdrm-pvr"
>  RCONFLICTS_${PN} = "omapdrm-pvr"
> 
> -BRANCH = "ti-img-sgx/${PV}/k4.9"
> +BRANCH = "ti-img-sgx/${PV}/k4.14"
> 
>  SRC_URI = "git://git.ti.com/graphics/omap5-sgx-ddk-linux.git;protocol=git;branch=${BRANCH} \
>  file://0001-srvkm-common-devicemem.c-suppress-implicit-fallthrou.patch<file:///\\0001-srvkm-common-devicemem.c-suppress-implicit-fallthrou.patch> \
> @@ -28,7 +28,7 @@ file://0001-srvkm-common-devicemem.c-suppress-implicit-fallthrou.patch<file:///\\0001-srvkm-common-devicemem.c-suppress-implicit-fallthrou.patch> \
> 
>  S = "${WORKDIR}/git"
> 
> -SRCREV = "0086977380d3320d70a3abc78b95fa0641427073"
> +SRCREV = "b144fa4b97cb69e54cabaad62daffcd4b5497c29"
> 
>  TARGET_PRODUCT_omap-a15 = "jacinto6evm"
>  TARGET_PRODUCT_ti33x = "ti335x"
> --
> 1.9.1
> 
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org<mailto:meta-ti@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/meta-ti

> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti



      reply	other threads:[~2018-04-03 21:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15  0:45 [rocko/master][PATCH v3] ti-sgx-ddk-km: update SGX kernel driver for k4.14 Eric Ruei
2018-03-15  0:51 ` Dmytriyenko, Denys
2018-03-15  0:58   ` Ruei, Eric
2018-03-15  0:59     ` Dmytriyenko, Denys
2018-04-03 21:00       ` Denys Dmytriyenko [this message]

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=20180403210048.GF31973@edge \
    --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.