Patchwork linux-yocto-dev: bump to v3.14-rc4

login
register
mail settings
Submitter Bruce Ashfield
Date Feb. 28, 2014, 2:28 p.m.
Message ID <1393597694-5843-1-git-send-email-bruce.ashfield@windriver.com>
Download mbox | patch
Permalink /patch/67717/
State Accepted
Commit d6596f5e0446b6aa3ae845389965bb2852f17b65
Headers show

Comments

Bruce Ashfield - Feb. 28, 2014, 2:28 p.m.
Updating the version of linux-yocto-dev to reflect the integration of
the 3.14-rc4 kernel.

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(-)
Bruce Ashfield - Feb. 28, 2014, 6:41 p.m.
FYI: Some extended testing with my image-core-kernel-dev image type
has shown that lttng and perf have some build issues, so we are
finding the issues that we wanted to with this -dev kernel :)

Cheers,

Bruce

On Fri, Feb 28, 2014 at 9:28 AM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> Updating the version of linux-yocto-dev to reflect the integration of
> the 3.14-rc4 kernel.
>
> 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 2b8c0556d0ed..5e097203e209 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -43,7 +43,7 @@ python () {
>              d.setVar("SRCREV_meta", "${AUTOREV}")
>  }
>
> -LINUX_VERSION ?= "3.13+"
> +LINUX_VERSION ?= "3.14+"
>  LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
>  PV = "${LINUX_VERSION}+git${SRCPV}"
>
> --
> 1.8.1.2
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
Richard Purdie - Feb. 28, 2014, 10:42 p.m.
On Fri, 2014-02-28 at 13:41 -0500, Bruce Ashfield wrote:
> FYI: Some extended testing with my image-core-kernel-dev image type
> has shown that lttng and perf have some build issues, so we are
> finding the issues that we wanted to with this -dev kernel :)

Yes, the autobuilder has shown up a raft of issues in that area.

http://autobuilder.yoctoproject.org/main/tgrid

the line starting 7a30f308b07... is pretty much all kernel related from
the dev kernel.

Cheers,

Richard
Bruce Ashfield - March 1, 2014, 1:54 a.m.
On Fri, Feb 28, 2014 at 5:42 PM, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> On Fri, 2014-02-28 at 13:41 -0500, Bruce Ashfield wrote:
>> FYI: Some extended testing with my image-core-kernel-dev image type
>> has shown that lttng and perf have some build issues, so we are
>> finding the issues that we wanted to with this -dev kernel :)
>
> Yes, the autobuilder has shown up a raft of issues in that area.
>
> http://autobuilder.yoctoproject.org/main/tgrid
>
> the line starting 7a30f308b07... is pretty much all kernel related from
> the dev kernel.

Yep, I consider the kernel available to BSp writers at the moment, the rest of
the failures need to be addressed by updating and fixing the packages.

That being said, I can never make heads or tails of those autobuilder
summaries .. what exactly would I click on to see if my builds and the
autobuilder have the same packages causing problems ?

Bruce

>
> Cheers,
>
> Richard
>
Richard Purdie - March 2, 2014, 5:56 p.m.
On Fri, 2014-02-28 at 20:54 -0500, Bruce Ashfield wrote:
> On Fri, Feb 28, 2014 at 5:42 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Fri, 2014-02-28 at 13:41 -0500, Bruce Ashfield wrote:
> >> FYI: Some extended testing with my image-core-kernel-dev image type
> >> has shown that lttng and perf have some build issues, so we are
> >> finding the issues that we wanted to with this -dev kernel :)
> >
> > Yes, the autobuilder has shown up a raft of issues in that area.
> >
> > http://autobuilder.yoctoproject.org/main/tgrid
> >
> > the line starting 7a30f308b07... is pretty much all kernel related from
> > the dev kernel.
> 
> Yep, I consider the kernel available to BSp writers at the moment, the rest of
> the failures need to be addressed by updating and fixing the packages.
> 
> That being said, I can never make heads or tails of those autobuilder
> summaries .. what exactly would I click on to see if my builds and the
> autobuilder have the same packages causing problems ?

On the above link you can see the horizontal line of boxes corresponding
to "7a30f308b07...". Each red box on that line is a failaure in that
build. "nightly" is a trigger of the others skip that one and click on
the "failed \n BuildImages \n Running Sanity Tests". You'll see some
"stdio" links under the failed targets. Click that and you'll see the
output of the failed build. Obviously if the image fails to build, the
sanity tests fail too so you'd usually start at the first red item.

I appreciate this navigation is a pain, its just what we have right now.
There is an error reporting tool (combination of a pastebin and
kerneloops.org) in the process of being deployed which should make this
much easier in future.

Cheers,

Richard

Patch

diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 2b8c0556d0ed..5e097203e209 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -43,7 +43,7 @@  python () {
             d.setVar("SRCREV_meta", "${AUTOREV}")
 }
 
-LINUX_VERSION ?= "3.13+"
+LINUX_VERSION ?= "3.14+"
 LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
 PV = "${LINUX_VERSION}+git${SRCPV}"