From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] linux-yocto/3.10: bump kver to v3.10.40
Date: Wed, 28 May 2014 14:47:31 +0100 [thread overview]
Message-ID: <1401284851.2607.49.camel@ted> (raw)
In-Reply-To: <5385DC75.6020902@windriver.com>
On Wed, 2014-05-28 at 08:54 -0400, Bruce Ashfield wrote:
> On 14-05-28 04:36 AM, Richard Purdie wrote:
> > On Mon, 2014-05-26 at 13:40 -0400, Bruce Ashfield wrote:
> >> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> >> index 7081cd18aa57..b1b80341d6d2 100644
> >> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> >> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.10.bb
> >> @@ -5,12 +5,12 @@ KBRANCH = "${KBRANCH_DEFAULT}"
> >> LINUX_KERNEL_TYPE = "tiny"
> >> KCONFIG_MODE = "--allnoconfig"
> >>
> >> -LINUX_VERSION ?= "3.10.38"
> >> +LINUX_VERSION ?= "3.10.40"
> >>
> >> KMETA = "meta"
> >>
> >> -SRCREV_machine ?= "02f7e63e56c061617957388c23bd5cf9b05c5388"
> >> -SRCREV_meta ?= "617c6158c3d5b931f0d6131e0b0a7b374c792599"
> >> +SRCREV_machine ?= "f53a6114b3a6e8c03ca4752de829887015f4c942"
> >> +SRCREV_meta ?= "13ae75f4a26fcd65abe526ef5f1dcde0583f453d"
> >
> > We're seeing failures since "13ae75f4a26fcd65abe526ef5f1dcde0583f453d"
> > doesn't appear to exist in the 3.10 tree meta branch. "bitbake -b
> > linux-yocto-tiny_3.10 -c fetch" reproduces.
> >
> > Did you miss pushing something?
>
> I don't manually push anything anymore, just my release scripts. I'll
> check to see if the infrastructure has let me down by re-running them
> now.
>
> .. and I did see the meta branch SRCREV push, and re-launched my
> builders. But all should be fine now.
>
> Sorry :(
No problem, these things happen. We just need to figure out what
happened and make sure it doesn't happen again. The commit is there now
so I'm guessing that should fix the build failures.
Cheers,
Richard
next prev parent reply other threads:[~2014-05-28 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 17:40 [PATCH 0/4] linux-yocto: consolidated kernel update Bruce Ashfield
2014-05-26 17:40 ` [PATCH 1/4] linux-yocto/3.14: update to v3.14.4 Bruce Ashfield
2014-05-26 17:40 ` [PATCH 2/4] linux-yocto-rt/3.14: update to 3.14-rt5 Bruce Ashfield
2014-05-26 17:40 ` [PATCH 3/4] beaglebone: enable the nowayout option for the watchdog Bruce Ashfield
2014-05-26 17:40 ` [PATCH 4/4] linux-yocto/3.10: bump kver to v3.10.40 Bruce Ashfield
2014-05-28 8:36 ` Richard Purdie
2014-05-28 12:54 ` Bruce Ashfield
2014-05-28 13:47 ` Richard Purdie [this message]
2014-05-28 13:52 ` Bruce Ashfield
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=1401284851.2607.49.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox