All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Sam Nelson <sam.nelson@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] ti-ipc: Update to new version 3.42.0.0_eng
Date: Fri, 5 Feb 2016 14:38:48 -0500	[thread overview]
Message-ID: <20160205193848.GW31480@edge> (raw)
In-Reply-To: <1454700538-7424-1-git-send-email-sam.nelson@ti.com>

Is it backward-compatible? Will it break any existing IPC uses?


On Fri, Feb 05, 2016 at 02:28:58PM -0500, Sam Nelson wrote:
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> ---
>  recipes-ti/ipc/ti-ipc.inc | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/recipes-ti/ipc/ti-ipc.inc b/recipes-ti/ipc/ti-ipc.inc
> index 94a1657..f3b1bff 100644
> --- a/recipes-ti/ipc/ti-ipc.inc
> +++ b/recipes-ti/ipc/ti-ipc.inc
> @@ -4,15 +4,15 @@ HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC"
>  LICENSE = "BSD"
>  LIC_FILES_CHKSUM = "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9b710fd7c95e545b91cec79255"
>  
> -BRANCH = "3.41"
> +BRANCH = "ipc-next"
>  
>  SRC_URI = "git://git.ti.com/ipc/ipcdev.git;protocol=git;branch=${BRANCH}"
>  
> -#Corresponds to 3.41.00.08
> -SRCREV = "7370abce2e3f2a09fd4b057fbbf9e7d3d029c0df"
> +#Corresponds to 3.42.00.00_eng
> +SRCREV = "2b47e35ed72170e4e56906fb9ab93dd9ef385a38"
>  
>  S = "${WORKDIR}/git"
> -PV = "3.41.00.08"
> +PV = "3.42.00.00"
>  INC_PR = "r0"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


  reply	other threads:[~2016-02-05 19:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 19:28 [PATCH] ti-ipc: Update to new version 3.42.0.0_eng Sam Nelson
2016-02-05 19:38 ` Denys Dmytriyenko [this message]
2016-02-05 22:12   ` Nelson, Sam

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=20160205193848.GW31480@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=sam.nelson@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.