From: Saul Wold <sgw@linux.intel.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Weekly build availability.
Date: Tue, 15 Jan 2013 20:44:19 -0800 [thread overview]
Message-ID: <50F63023.80306@linux.intel.com> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A83C8B0@039-SN1MPN1-001.039d.mgd.msft.net>
On 01/15/2013 08:37 PM, McClintock Matthew-B29882 wrote:
> On Tue, Jan 15, 2013 at 7:09 PM, Flanagan, Elizabeth
> <elizabeth.flanagan@intel.com> wrote:
>> - p1022ds failed due to a libxml2_2.8.0 failure. it is also throwing
>> warnings about missing patches.
>
> I've got a master-next branch I'm testing now and should be on master
> soon. I'm also debugging the oprofile issues from nightly-ppc as well.
>
There is a patch from Bogdan for this one, see "oprofile: set correct
kernel path", there is clearly more work needed here, but that will get
us past this failure until we get the libpfm recipe in, which looks like
it will be required also.
Sau!
> -M
>
>
next prev parent reply other threads:[~2013-01-16 4:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 1:09 Weekly build availability Flanagan, Elizabeth
2013-01-16 1:52 ` Saul Wold
2013-01-16 4:37 ` McClintock Matthew-B29882
2013-01-16 4:44 ` Saul Wold [this message]
2013-01-16 4:55 ` McClintock Matthew-B29882
-- strict thread matches above, loose matches on Subject: below --
2013-12-11 19:11 Flanagan, Elizabeth
2013-11-19 19:32 Flanagan, Elizabeth
2013-08-21 0:07 Flanagan, Elizabeth
2013-07-17 6:35 Flanagan, Elizabeth
2013-06-18 23:03 Flanagan, Elizabeth
2013-05-22 0:40 Flanagan, Elizabeth
2013-03-14 7:27 Weekly Build availability Flanagan, Elizabeth
2013-03-06 3:21 Weekly build availability Flanagan, Elizabeth
2013-03-06 7:11 ` Flanagan, Elizabeth
2013-02-14 16:58 Flanagan, Elizabeth
2012-12-27 0:09 Weekly Build Availability Flanagan, Elizabeth
2012-12-19 23:54 Weekly build availability Flanagan, Elizabeth
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=50F63023.80306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=B29882@freescale.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.