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] linux-yocto-dev: bump to v3.14-rc4
Date: Fri, 28 Feb 2014 22:42:13 +0000 [thread overview]
Message-ID: <1393627333.20876.2.camel@ted> (raw)
In-Reply-To: <CADkTA4OEvrDPDPq3-cKsX+_gN_qgR_dEVJKPWvkM2bV1TW0NHQ@mail.gmail.com>
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
next prev parent reply other threads:[~2014-02-28 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 14:28 [PATCH] linux-yocto-dev: bump to v3.14-rc4 Bruce Ashfield
2014-02-28 18:41 ` Bruce Ashfield
2014-02-28 22:42 ` Richard Purdie [this message]
2014-03-01 1:54 ` Bruce Ashfield
2014-03-02 17:56 ` Richard Purdie
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=1393627333.20876.2.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