Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] linux-yocto: 3.4, 3.10 and 3.14 updates
Date: Wed, 18 Jun 2014 10:33:14 +0100	[thread overview]
Message-ID: <1403083994.2104.7.camel@ted> (raw)
In-Reply-To: <CADkTA4NzmohFfDh1h9dobBEVC+CRum1-AeFQABVSV6O4NBi34w@mail.gmail.com>

On Tue, 2014-06-17 at 21:08 -0400, Bruce Ashfield wrote:
> On Tue, Jun 17, 2014 at 8:20 PM, Bruce Ashfield
> <bruce.ashfield@windriver.com> wrote:
> > On 2014-06-17, 6:18 PM, Richard Purdie wrote:
> >>
> >> On Tue, 2014-06-17 at 11:26 -0400, Bruce Ashfield wrote:
> >>>
> >>> Richard/Saul,
> >>>
> >>> Here are my collect stable updates to 3.4 -> 3.14. Build and boot sanity
> >>> passed here, but with three versions being updated, its a lot of build
> >>> testing :)
> >>>
> >>> I also have an update for NAND support on the mpc8315e reference board,
> >>> which allows us to shake out flash filesystem issues. I'll follow up
> >>> with a meta-yocto-bsp change to enable the changes there as well.
> >>
> >>
> >> I merged these two series and we've started seeing:
> >>
> >> https://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/119
> >>
> >> which is a 3.14 kernel lttng-modules failure on the autobuilder :(
> >>
> >> Are we missing an update to lttng?
> >
> >
> > I reproduced the breakage with a fresh tree. I'll fire off a patch tonight
> > with any amount of luck :)
> >
> 
> No luck needed. lttng 2.4.1-stable already has a fix, once my build completes
> against 3.10, I'll send the SRCREV update.

Much appreciated, thanks!

Richard



      reply	other threads:[~2014-06-18  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 15:26 [PATCH 0/5] linux-yocto: 3.4, 3.10 and 3.14 updates Bruce Ashfield
2014-06-17 15:26 ` [PATCH 1/5] linux-yocto/3.10: update to v3.10.41 Bruce Ashfield
2014-06-17 15:26 ` [PATCH 2/5] linux-yocto/3.14: update to v3.14.5 Bruce Ashfield
2014-06-17 15:26 ` [PATCH 3/5] linux-yocto/3.4: update to v3.4.91 Bruce Ashfield
2014-06-17 15:26 ` [PATCH 4/5] linux-yocto/3.14: enable mpc8315e NAND and Yaffs2 gcc 4.9 fix Bruce Ashfield
2014-06-17 15:26 ` [PATCH 5/5] linux-yocto/3.10: update to v3.10.43 Bruce Ashfield
2014-06-17 22:18 ` [PATCH 0/5] linux-yocto: 3.4, 3.10 and 3.14 updates Richard Purdie
2014-06-18  0:01   ` Bruce Ashfield
2014-06-18  0:20   ` Bruce Ashfield
2014-06-18  1:08     ` Bruce Ashfield
2014-06-18  9:33       ` Richard Purdie [this message]

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=1403083994.2104.7.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@gmail.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