All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 2/4] u-boot-ti-staging: add the latest integration tree in prep for 2013.10 release
Date: Fri, 23 Aug 2013 16:08:30 -0400	[thread overview]
Message-ID: <20130823200830.GA7108@denix.org> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED101596DEFAC@DLEE11.ent.ti.com>

On Fri, Aug 23, 2013 at 08:05:55PM +0000, Maupin, Chase wrote:
> >-----Original Message-----
> >From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> >bounces@yoctoproject.org] On Behalf Of Denys Dmytriyenko
> >Sent: Friday, August 23, 2013 2:58 PM
> >To: meta-ti@yoctoproject.org
> >Subject: [meta-ti] [PATCH 2/4] u-boot-ti-staging: add the latest
> >integration tree in prep for 2013.10 release
> >
> >From: Denys Dmytriyenko <denys@ti.com>
> >
> >Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> >---
> > recipes-bsp/u-boot/u-boot-ti-staging_git.bb | 19
> >+++++++++++++++++++
> > 1 file changed, 19 insertions(+)
> > create mode 100644 recipes-bsp/u-boot/u-boot-ti-staging_git.bb
> >
> >diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_git.bb
> >b/recipes-bsp/u-boot/u-boot-ti-staging_git.bb
> >new file mode 100644
> >index 0000000..bd6188d
> >--- /dev/null
> >+++ b/recipes-bsp/u-boot/u-boot-ti-staging_git.bb
> >@@ -0,0 +1,19 @@
> >+require u-boot-ti.inc
> >+
> >+DESCRIPTION = "u-boot bootloader for TI devices"
> >+
> >+LIC_FILES_CHKSUM =
> >"file://Licenses/README;md5=6bc50ecab884fce80cd3ef3da8852b08"
> >+
> >+PV = "2013.09+2013.10-rc1"
> 
> Shouldn't this be more 2013.07+2013.10-rc1?

Yes, I believe you are right - u-boot uses quarterly releases, but messes up 
my mind by using YYYY.MM format :)


> Also, will you update the other machines like dra7xx-evm to use this tree?

Sure, if we need to. 2013.07 would probably be better, as this is supposed to 
be unstable.


> >+PR = "r0+gitr${SRCPV}"
> >+
> >+DEFAULT_PREFERENCE = "-1"
> >+
> >+SRC_URI = "git://git.ti.com/ti-u-boot/ti-u-
> >boot.git;protocol=git;branch=${BRANCH}"
> >+
> >+BRANCH ?= "master"
> >+
> >+SRCREV = "39bc12ddc36c9e30199471da0f3a929b178a04b2"
> >+
> >+SPL_BINARY = "MLO"
> >+SPL_UART_BINARY = "u-boot-spl.bin"
> >--
> >1.8.3.2
> >
> >_______________________________________________
> >meta-ti mailing list
> >meta-ti@yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/meta-ti
> 


  reply	other threads:[~2013-08-23 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-23 19:58 [PATCH 1/4] linux-ti-staging: add the latest integration tree in prep for 3.12 release Denys Dmytriyenko
2013-08-23 19:58 ` [PATCH 2/4] u-boot-ti-staging: add the latest integration tree in prep for 2013.10 release Denys Dmytriyenko
2013-08-23 20:05   ` Maupin, Chase
2013-08-23 20:08     ` Denys Dmytriyenko [this message]
2013-08-23 19:58 ` [PATCH 3/4] ti43x: add new SOC family for Sitara AM43xx Cortex-A9 processors Denys Dmytriyenko
2013-08-23 20:07   ` Maupin, Chase
2013-08-23 19:58 ` [PATCH 4/4] am437x-evm: add machine config for Sitara AM437x EVM Denys Dmytriyenko
2013-08-23 20:07   ` Maupin, Chase
2013-08-23 20:03 ` [PATCH 1/4] linux-ti-staging: add the latest integration tree in prep for 3.12 release Maupin, Chase
2013-08-23 20:05   ` 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=20130823200830.GA7108@denix.org \
    --to=denys@ti.com \
    --cc=chase.maupin@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.