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 09:36:39 +0100 [thread overview]
Message-ID: <1401266199.2607.15.camel@ted> (raw)
In-Reply-To: <81e37d5db466c157a8ca0069c60102eb12616532.1401124899.git.bruce.ashfield@windriver.com>
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?
We're seeing failures on the autobuilder as I've merged this :/.
Cheers,
Richard
next prev parent reply other threads:[~2014-05-28 8:36 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 [this message]
2014-05-28 12:54 ` Bruce Ashfield
2014-05-28 13:47 ` Richard Purdie
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=1401266199.2607.15.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