From: Saul Wold <sgw@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/8] linux-yocto-dev: bump to v3.16+
Date: Thu, 24 Jul 2014 20:35:19 -0700 [thread overview]
Message-ID: <53D1D077.5020009@linux.intel.com> (raw)
In-Reply-To: <a2203c27a84c25e8e62fde8b24e5c829ca212fe2.1406234258.git.bruce.ashfield@windriver.com>
On 07/24/2014 01:41 PM, Bruce Ashfield wrote:
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> index 9b49eee87651..10f3d234ed25 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -36,7 +36,7 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;bareclone=1;branch=${K
> SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
> SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
>
> -LINUX_VERSION ?= "3.14+"
> +LINUX_VERSION ?= "3.16+"
> LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
> PV = "${LINUX_VERSION}+git${SRCPV}"
>
>
So far the Autobuilder has found 1 issue with this and the x32 build
https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/182/steps/BuildImages/logs/stdio
I will send more failures as I see them.
Sau!
next prev parent reply other threads:[~2014-07-25 3:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 20:41 [PATCH 0/8] kernel: linux-yocto 3.14, linux-yocto-dev 3.16 and dependencies Bruce Ashfield
2014-07-24 20:41 ` [PATCH 1/8] linux-yocto/3.14: vexpress and MVM firmware support Bruce Ashfield
2014-07-24 20:41 ` [PATCH 2/8] lttng-modules: update to 2.5.0 Bruce Ashfield
2014-07-25 13:21 ` Martin Jansa
2014-07-25 13:23 ` Bruce Ashfield
2014-07-25 13:36 ` Bruce Ashfield
2014-07-25 13:46 ` Martin Jansa
2014-07-25 13:48 ` Bruce Ashfield
2014-07-25 14:41 ` Richard Purdie
2014-08-12 11:33 ` Martin Jansa
2014-08-12 11:50 ` Laurentiu Palcu
2014-07-24 20:41 ` [PATCH 3/8] linux-yocto: x86_64: expand kernel stack to 16K Bruce Ashfield
2014-07-24 20:41 ` [PATCH 4/8] linux-yocto-dev: bump to v3.16+ Bruce Ashfield
2014-07-25 3:35 ` Saul Wold [this message]
2014-07-25 3:36 ` Bruce Ashfield
2014-07-25 3:44 ` Bruce Ashfield
2014-07-24 20:41 ` [PATCH 5/8] kernel: don't copy .so.dbg files into kernel source install Bruce Ashfield
2014-07-24 20:41 ` [PATCH 6/8] lttng-modules: re-enable ARM builds Bruce Ashfield
2014-07-24 22:02 ` Martin Jansa
2014-07-25 3:10 ` Bruce Ashfield
2014-07-25 9:53 ` Martin Jansa
2014-07-25 13:00 ` Bruce Ashfield
2014-07-25 13:14 ` Bruce Ashfield
2014-07-24 20:41 ` [PATCH 7/8] linux-yocto/3.14: libata and generic CPU modalias handling Bruce Ashfield
2014-07-24 20:41 ` [PATCH 8/8] kern-tools: adjust to full history meta-data 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=53D1D077.5020009@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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