From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org, saul.wold@intel.com
Subject: Re: [PATCH 0/1] linux-yocto: add jasperforest BSP and fix lttng NMI bug
Date: Tue, 15 Feb 2011 14:32:01 -0500 [thread overview]
Message-ID: <4D5AD4B1.5080107@windriver.com> (raw)
In-Reply-To: <1297798090.4945.374.camel@rex>
On 11-02-15 02:28 PM, Richard Purdie wrote:
> On Tue, 2011-02-15 at 14:07 -0500, Bruce Ashfield wrote:
>> Richard/Saul,
>>
>> During the introduction of the jasperforest BSP, a lttng
>> issues was picked up with NMI tracing. The upstream (and
>> our solution) is to revert that commit.
>>
>> This change updates the meta repo for jasperforest and pushes
>> out the nmi revert to all BSPs.
>>
>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>> Branch: zedd/jasperforest
>> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/jasperforest
>>
>> Thanks,
>> Bruce Ashfield<bruce.ashfield@windriver.com>
>> ---
>>
>>
>> Bruce Ashfield (1):
>> linux-yocto: add jasperforest BSP and fix lttng NMI bug
>>
>> .../conf/distro/include/poky-default-revisions.inc | 27 +++++++++----------
>> 1 files changed, 13 insertions(+), 14 deletions(-)
>
> btw, this is not all this branch contains. Luckily I noticed and caught
> that :)
urk. I pushed my master AND not the jasperforest branch
that I created for the submission.
Rushing as usual causes mistakes .. sorry about that.
Bruce
>
> Cheers,
>
> Richard
>
>
prev parent reply other threads:[~2011-02-15 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 19:07 [PATCH 0/1] linux-yocto: add jasperforest BSP and fix lttng NMI bug Bruce Ashfield
2011-02-15 19:07 ` [PATCH 1/1] " Bruce Ashfield
2011-02-15 19:25 ` [PATCH 0/1] " Richard Purdie
2011-02-15 19:28 ` Richard Purdie
2011-02-15 19:32 ` Bruce Ashfield [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=4D5AD4B1.5080107@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.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.