From: Denys Dmytriyenko <denys@ti.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH 2/2] linux-ti-staging 3.14: update to latest 3.14.15 plus connectivity changes
Date: Mon, 4 Aug 2014 10:13:06 -0400 [thread overview]
Message-ID: <20140804141306.GP15788@edge> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C6F1BDF@DFLE08.ent.ti.com>
Unfortunately, this breaks Darren's SGX patches... :( Moreover, we already
pick this update up due to AUTOREV in meta-arago, so nightlies have been
failing for couple days. Need to look into those patches and update them.
On Mon, Aug 04, 2014 at 01:56:27PM +0000, Cooper Jr., Franklin wrote:
> Acked-by: Franklin Cooper Jr. <fcooper@ti.com>
>
> > -----Original Message-----
> > From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> > bounces@yoctoproject.org] On Behalf Of Denys Dmytriyenko
> > Sent: Saturday, August 02, 2014 8:11 PM
> > To: meta-ti@yoctoproject.org
> > Subject: [meta-ti] [PATCH 2/2] linux-ti-staging 3.14: update to latest 3.14.15
> > plus connectivity changes
> >
> > From: Denys Dmytriyenko <denys@ti.com>
> >
> > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > ---
> > recipes-kernel/linux/linux-ti-staging_3.14.bb | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/recipes-kernel/linux/linux-ti-staging_3.14.bb b/recipes-
> > kernel/linux/linux-ti-staging_3.14.bb
> > index c223c88..7abaeac 100644
> > --- a/recipes-kernel/linux/linux-ti-staging_3.14.bb
> > +++ b/recipes-kernel/linux/linux-ti-staging_3.14.bb
> > @@ -43,11 +43,11 @@ S = "${WORKDIR}/git"
> >
> > BRANCH = "ti-linux-3.14.y"
> >
> > -SRCREV = "b0fa4f08d72c8723219b5174b5749151b5acaee0"
> > -PV = "3.14.14"
> > +SRCREV = "aa595e6598fc5a722ee653881334d0d8a16477bc"
> > +PV = "3.14.15"
> >
> > # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a
> > rebuild -MACHINE_KERNEL_PR_append = "b+gitr${SRCPV}"
> > +MACHINE_KERNEL_PR_append = "a+gitr${SRCPV}"
> > PR = "${MACHINE_KERNEL_PR}"
> >
> > KERNEL_CONFIG_DIR = "${S}/ti_config_fragments"
> > --
> > 2.0.2
> >
> > --
> > _______________________________________________
> > 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
next prev parent reply other threads:[~2014-08-04 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 1:11 [PATCH 1/2] linux-ti-staging 3.12: update to latest 3.12.26 Denys Dmytriyenko
2014-08-03 1:11 ` [PATCH 2/2] linux-ti-staging 3.14: update to latest 3.14.15 plus connectivity changes Denys Dmytriyenko
2014-08-04 13:56 ` Cooper Jr., Franklin
2014-08-04 14:13 ` Denys Dmytriyenko [this message]
2014-08-04 13:56 ` [PATCH 1/2] linux-ti-staging 3.12: update to latest 3.12.26 Cooper Jr., Franklin
-- strict thread matches above, loose matches on Subject: below --
2014-08-01 17:39 Denys Dmytriyenko
2014-08-01 17:39 ` [PATCH 2/2] linux-ti-staging 3.14: update to latest 3.14.15 plus connectivity changes Denys Dmytriyenko
2014-08-04 13:56 ` Cooper Jr., Franklin
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=20140804141306.GP15788@edge \
--to=denys@ti.com \
--cc=fcooper@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.