All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Karthik Ramanan <a0393906@ti.com>
Cc: meta-ti@yoctoproject.org, "Anna, Suman" <s-anna@ti.com>
Subject: Re: [krogoth] ti-ipc: update to 3.45.00.00
Date: Mon, 27 Feb 2017 13:20:08 -0500	[thread overview]
Message-ID: <20170227182008.GB11106@edge> (raw)
In-Reply-To: <1487994622-87927-1-git-send-email-a0393906@ti.com>

Karthik,

Why are you upgrading IPC in krogoth to 3.45? I thought that was mainly to 
work with 4.9 kernel...

-- 
Denys


On Sat, Feb 25, 2017 at 09:20:22AM +0530, Karthik Ramanan wrote:
> Signed-off-by: Karthik Ramanan <a0393906@ti.com>
> ---
>  recipes-ti/ipc/ti-ipc-common.inc |  2 +-
>  recipes-ti/ipc/ti-ipc-rtos.inc   | 10 +++++-----
>  recipes-ti/ipc/ti-ipc.inc        |  6 +++---
>  3 files changed, 9 insertions(+), 9 deletions(-)
> 
> diff --git a/recipes-ti/ipc/ti-ipc-common.inc b/recipes-ti/ipc/ti-ipc-common.inc
> index 8a2aa0a..6aa08c5 100644
> --- a/recipes-ti/ipc/ti-ipc-common.inc
> +++ b/recipes-ti/ipc/ti-ipc-common.inc
> @@ -1,4 +1,4 @@
> -PV = "3.44.01.01"
> +PV = "3.45.00.00"
>  INC_PR = "r0"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> diff --git a/recipes-ti/ipc/ti-ipc-rtos.inc b/recipes-ti/ipc/ti-ipc-rtos.inc
> index 1c509b0..332f238 100644
> --- a/recipes-ti/ipc/ti-ipc-rtos.inc
> +++ b/recipes-ti/ipc/ti-ipc-rtos.inc
> @@ -25,16 +25,16 @@ protocol=${TI_IPC_METADATA_GIT_PROTOCOL};\
>  branch=${TI_IPC_METADATA_GIT_BRANCH};\
>  name=${TI_IPC_METADATA_NAME}"
>  
> -# Corresponds to tag: 3.44.01.01
> -SRCREV_ipc-examples = "b19a3b7a003aa3304a12599a498d9b3a24f20c6e"
> +# Corresponds to tag: 3.45.00.00
> +SRCREV_ipc-examples = "3a8ee1841ec36117a9bcd3d45bb2781bbd53ecf8"
>  
> -# Corresponds to tag: 3.44.01.01
> -SRCREV_ipc-metadata = "a21264bdbb1b64d41bbcb4e6bb17d2c1d4ccb839"
> +# Corresponds to tag: 3.45.00.00
> +SRCREV_ipc-metadata = "30b83f09be1877f86b22c971d978cb478fc7dd6e"
>  
>  S_ipc-examples = "${WORKDIR}/git/ipc-examples"
>  S_ipc-metadata = "${WORKDIR}/git/ipc-metadata"
>  
> -PR = "${INC_PR}.0"
> +PR = "${INC_PR}.1"
>  
>  DEPENDS_append_keystone = " ti-cgt6x-native \
>                              gcc-arm-none-eabi-native \
> diff --git a/recipes-ti/ipc/ti-ipc.inc b/recipes-ti/ipc/ti-ipc.inc
> index 3ac8bf5..ea256d2 100644
> --- a/recipes-ti/ipc/ti-ipc.inc
> +++ b/recipes-ti/ipc/ti-ipc.inc
> @@ -6,10 +6,10 @@ LIC_FILES_CHKSUM = "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9
>  
>  TI_IPC_GIT_URI = "git://git.ti.com/ipc/ipcdev.git"
>  TI_IPC_GIT_PROTOCOL = "git"
> -TI_IPC_GIT_BRANCH = "ipc-3.44-next"
> +TI_IPC_GIT_BRANCH = "master"
>  
> -#Corresponds to 3.44.01.01
> -TI_IPC_SRCREV = "cff640a4c7e083f78116266ef681cec49d9b584b"
> +#Corresponds to 3.45.00.00
> +TI_IPC_SRCREV = "1584985938884bf6cb1d839779578354b1865ea4"
>  
>  BRANCH = "${TI_IPC_GIT_BRANCH}"
>  SRC_URI = "${TI_IPC_GIT_URI};protocol=${TI_IPC_GIT_PROTOCOL};branch=${BRANCH};name=ipcdev"
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


  reply	other threads:[~2017-02-27 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-25  3:50 [krogoth] ti-ipc: update to 3.45.00.00 Karthik Ramanan
2017-02-27 18:20 ` Denys Dmytriyenko [this message]
2017-02-27 18:25   ` Suman Anna

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=20170227182008.GB11106@edge \
    --to=denys@ti.com \
    --cc=a0393906@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=s-anna@ti.com \
    /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.