All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Siddharth Heroor <heroor@ti.com>
Subject: Re: [PATCHv3 4/5] ti-syslink-module: Add Syslink version	02.00.00.68 Beta1
Date: Sun, 17 Apr 2011 14:27:30 -0400	[thread overview]
Message-ID: <20110417182730.GC4068@denix.org> (raw)
In-Reply-To: <1302319620-18223-4-git-send-email-heroor@gmail.com>

On Sat, Apr 09, 2011 at 08:56:59AM +0530, Siddharth Heroor wrote:
> From: Siddharth Heroor <heroor@ti.com>
> 
> 
> Signed-off-by: Siddharth Heroor <heroor@ti.com>
> ---
>  ...-syslink-module_02.00.00.67+02.00.00.68beta1.bb |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
>  create mode 100644 recipes/ti/ti-syslink-module_02.00.00.67+02.00.00.68beta1.bb

Sid,

Renaming the file with the proper versioning doesn't do any good, when you set 
the actual PV inside the recipe to the wrong value anyway - bitbake and opkg 
will sort by PV and not the recipe name! Hence, you are setting the version to 
02_00_00_68 and what happens when the real 02_00_00_68 gets released?

I did some quick editing and will send the updated patches for #4 and #5 - 
please review and provide feedback. Thanks.

-- 
Denys

> diff --git a/recipes/ti/ti-syslink-module_02.00.00.67+02.00.00.68beta1.bb b/recipes/ti/ti-syslink-module_02.00.00.67+02.00.00.68beta1.bb
> new file mode 100644
> index 0000000..f7bcb35
> --- /dev/null
> +++ b/recipes/ti/ti-syslink-module_02.00.00.67+02.00.00.68beta1.bb
> @@ -0,0 +1,11 @@
> +require ti-syslink-module.inc
> +
> +PV = "02_00_00_68"
> +PVExtra = "_beta1"
> +
> +S = "${WORKDIR}/syslink_${PV}${PVExtra}/ti/syslink/utils/hlos/knl/Linux"
> +SYSLINK_ROOT = "${WORKDIR}/syslink_${PV}${PVExtra}"
> +
> +SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/SysLink/${PV}${PVExtra}/exports/syslink_${PV}${PVExtra}.tar.gz;name=syslinktarball"
> +SRC_URI[syslinktarball.md5sum] = "468034372124f70f82b60cfb5f11c8e8"
> +SRC_URI[syslinktarball.sha256sum] = "ed574dcb3a5477cfbc69a1c9e768d5197291cb057d19fd791e16e1c89af3e8e1"
> -- 
> 1.7.0.4
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2011-04-17 18:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-09  3:26 [PATCHv3 1/5] ti-syslink: Add TI Syslink Common include file Siddharth Heroor
2011-04-09  3:26 ` [PATCHv3 2/5] ti-syslink: Add include file for Syslink Module Siddharth Heroor
2011-04-09  3:26 ` [PATCHv3 3/5] ti-syslink: Add include file for Syslink Libraries Siddharth Heroor
2011-04-09  3:26 ` [PATCHv3 4/5] ti-syslink-module: Add Syslink version 02.00.00.68 Beta1 Siddharth Heroor
2011-04-17 18:27   ` Denys Dmytriyenko [this message]
2011-04-17 18:32     ` [PATCHv4 " Denys Dmytriyenko
2011-04-18  3:01     ` [PATCHv3 " Siddharth Heroor
2011-04-18  3:15       ` Denys Dmytriyenko
2011-04-18  4:14         ` Siddharth Heroor
2011-04-09  3:27 ` [PATCHv3 5/5] ti-syslink-libs: " Siddharth Heroor
2011-04-16 21:34   ` Xianghua Xiao
2011-04-17  0:11     ` Denys Dmytriyenko
2011-04-17 18:33   ` [PATCHv4 " 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=20110417182730.GC4068@denix.org \
    --to=denis@denix.org \
    --cc=heroor@ti.com \
    --cc=openembedded-devel@lists.openembedded.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.