All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Jacob Stiffler <j-stiffler@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [PATCH 2/3] oc: bump SRCREV to version 1.1.10.0
Date: Fri, 16 Sep 2016 12:22:21 -0400	[thread overview]
Message-ID: <20160916162221.GX29658@edge> (raw)
In-Reply-To: <20fa2d84-19d8-f051-4404-6d539700e26a@ti.com>

On Fri, Sep 16, 2016 at 12:21:13PM -0400, Jacob Stiffler wrote:
> 
> 
> On 9/16/2016 12:13 PM, Denys Dmytriyenko wrote:
> >On Fri, Sep 16, 2016 at 05:54:34AM -0400, Stiffler, Jacob wrote:
> >>>-----Original Message-----
> >>>From: Dmytriyenko, Denys
> >>>Sent: Thursday, September 15, 2016 3:29 PM
> >>>To: Stiffler, Jacob
> >>>Cc: meta-arago@arago-project.org
> >>>Subject: Re: [meta-arago] [PATCH 2/3] oc: bump SRCREV to version 1.1.10.0
> >>>
> >>>>oc: bump SRCREV to version 1.1.10.0
> >>>Should it be ocl in the subject?
> >>>
> >>Yes. And I just found out a 1.1.10.1 version is happening. I'll resubmit
> >>with the new SRCREV and fix the comit message.
> >Will you be resubmitting all 3 patches or only #2?
> 
> Only #2.

Sorry, I meant to ask if I should push #1 and #3 now w/o #2 or should I wait 
for you to resubmit #2 and keep the order?


> >>>On Thu, Sep 15, 2016 at 02:35:08PM -0400, Jacob Stiffler wrote:
> >>>>Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
> >>>>---
> >>>>  meta-arago-extras/recipes-ti/ocl/ocl.inc | 4 ++--
> >>>>  1 file changed, 2 insertions(+), 2 deletions(-)
> >>>>
> >>>>diff --git a/meta-arago-extras/recipes-ti/ocl/ocl.inc b/meta-arago-
> >>>extras/recipes-ti/ocl/ocl.inc
> >>>>index 4df0c9e..1937a3f 100644
> >>>>--- a/meta-arago-extras/recipes-ti/ocl/ocl.inc
> >>>>+++ b/meta-arago-extras/recipes-ti/ocl/ocl.inc
> >>>>@@ -1,4 +1,4 @@
> >>>>-PV = "1.1.9.1"
> >>>>+PV = "1.1.10.0"
> >>>>  INC_PR = "r0"
> >>>>
> >>>>  LIC_FILES_CHKSUM =
> >>>"file://../debian/copyright;md5=2e3965a73a8a49c23836467266120dff"
> >>>>@@ -9,7 +9,7 @@ OCL_GIT_URI = "git://git.ti.com/opencl/ti-opencl.git"
> >>>>  OCL_GIT_PROTOCOL = "git"
> >>>>  OCL_GIT_BRANCH = "master"
> >>>>
> >>>>-OCL_SRCREV = "aa89b7359d6328e98fa80c55c3b73543c53a1bbc"
> >>>>+OCL_SRCREV = "b2b6c17a40bc79f49b6cdc44b6a42faeb56a6d2f"
> >>>>
> >>>>  BRANCH = "${OCL_GIT_BRANCH}"
> >>>>  SRC_URI =
> >>>"${OCL_GIT_URI};protocol=${OCL_GIT_PROTOCOL};branch=${BRANCH}"
> >>>>--
> >>>>2.7.4
> >>>>
> >>>>_______________________________________________
> >>>>meta-arago mailing list
> >>>>meta-arago@arago-project.org
> >>>>http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> 


  reply	other threads:[~2016-09-16 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 18:35 [PATCH 1/3] ti-llvm3.6: bump SRCREV for updates Jacob Stiffler
2016-09-15 18:35 ` [PATCH 2/3] oc: bump SRCREV to version 1.1.10.0 Jacob Stiffler
2016-09-15 19:29   ` Denys Dmytriyenko
2016-09-16  9:54     ` Stiffler, Jacob
2016-09-16 16:13       ` Denys Dmytriyenko
2016-09-16 16:21         ` Jacob Stiffler
2016-09-16 16:22           ` Denys Dmytriyenko [this message]
2016-09-16 16:24             ` Jacob Stiffler
2016-09-15 18:35 ` [PATCH 3/3] openmpacc: bump SRCREV to version 1.4.0.0 Jacob Stiffler

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=20160916162221.GX29658@edge \
    --to=denys@ti.com \
    --cc=j-stiffler@ti.com \
    --cc=meta-arago@arago-project.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.