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 1/3] linux-ti-staging: update to the latest merge	of 3.8.3
Date: Mon, 18 Mar 2013 14:46:28 -0400	[thread overview]
Message-ID: <20130318184628.GK32759@edge> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED10159481C2B@DLEE11.ent.ti.com>

On Mon, Mar 18, 2013 at 06:43:52PM +0000, Maupin, Chase wrote:
> > -----Original Message-----
> > From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> > bounces@yoctoproject.org] On Behalf Of Denys Dmytriyenko
> > Sent: Monday, March 18, 2013 1:41 PM
> > To: meta-ti@yoctoproject.org
> > Subject: [meta-ti] [PATCH 1/3] linux-ti-staging: update to the
> > latest merge of 3.8.3
> 
> Acked-by: Chase Maupin <chase.maupin@ti.com>
> 
> Although, we may still need to do version specific (non _git) versions of 
> the recipes when there is an official release.

When and if we have a long-term releases of the ti-staging kernel tree, we can 
revisit this. But for now it would be too much churn to rename the recipe 
every week with every next re-merge...

-- 
Denys


> > From: Denys Dmytriyenko <denys@ti.com>
> > 
> > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > ---
> >  recipes-kernel/linux/linux-ti-staging_git.bb | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/recipes-kernel/linux/linux-ti-staging_git.bb
> > b/recipes-kernel/linux/linux-ti-staging_git.bb
> > index dfef76d..605fbc1 100644
> > --- a/recipes-kernel/linux/linux-ti-staging_git.bb
> > +++ b/recipes-kernel/linux/linux-ti-staging_git.bb
> > @@ -39,11 +39,11 @@ S = "${WORKDIR}/git"
> > 
> >  BRANCH = "ti-linux-3.8.y"
> > 
> > -SRCREV = "e69f39916783a559c499e264359edea315ef44fd"
> > -PV = "3.8.2"
> > +SRCREV = "ed93a28fb0b1dc28cc252ee87f6fce3e07bf23fe"
> > +PV = "3.8.3"
> > 
> >  # Append to the MACHINE_KERNEL_PR so that a new SRCREV will
> > cause a rebuild
> > -MACHINE_KERNEL_PR_append = "d+gitr${SRCPV}"
> > +MACHINE_KERNEL_PR_append = "a+gitr${SRCPV}"
> > 
> >  SRC_URI = "git://gitorious.ti.com/ti-linux-kernel/ti-linux-
> > kernel.git;protocol=git;branch=${BRANCH} \
> >             file://defconfig \
> > --
> > 1.8.1.5
> > 
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti


  reply	other threads:[~2013-03-18 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 18:40 [PATCH 1/3] linux-ti-staging: update to the latest merge of 3.8.3 Denys Dmytriyenko
2013-03-18 18:40 ` [PATCH 2/3] am335x, beaglebone: switch default preference to ti-staging tree Denys Dmytriyenko
2013-03-18 18:45   ` Maupin, Chase
2013-03-18 18:47     ` Denys Dmytriyenko
2013-03-18 18:40 ` [PATCH 3/3] linux-ti33x-psp 3.1: remove an older outdated 3.1 kernel recipe for ti33x Denys Dmytriyenko
2013-03-18 18:45   ` Maupin, Chase
2013-03-18 18:43 ` [PATCH 1/3] linux-ti-staging: update to the latest merge of 3.8.3 Maupin, Chase
2013-03-18 18:46   ` Denys Dmytriyenko [this message]
2013-03-18 18:47     ` Maupin, Chase

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=20130318184628.GK32759@edge \
    --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.