From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org, poky@yoctoproject.org
Subject: Re: [PATCH 0/1] perf: hard-code NO_LIBPERL/NO_LIBPYTHO
Date: Tue, 25 Jan 2011 09:20:58 -0800 [thread overview]
Message-ID: <4D3F067A.2040103@intel.com> (raw)
In-Reply-To: <cover.1295970827.git.bruce.ashfield@windriver.com>
On 01/25/2011 07:59 AM, Bruce Ashfield wrote:
> We already had this fix in the 2.6.37 kernel (and it is staged
> temporarily there) so this is the same change for the -stable
> kernel to fix the perf build error reported by Gary this morning.
>
> I went ahead and merged this to the kernel tree directly, since
> we may not loop back and do another fix for this on in the -stable
> kernel.
>
> Compiled for atom-pc/beagleboard and routerstationpro.
>
Does this mean we can revert the patch in perl and python recipes?
Sau!
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: zedd/kernel-stable
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-stable
>
> Thanks,
> Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (1):
> linux-yocto/stable: perf: hard-code NO_LIBPERL/NO_LIBPYTHO
>
> .../conf/distro/include/poky-default-revisions.inc | 18 +++++++++---------
> 1 files changed, 9 insertions(+), 9 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
next prev parent reply other threads:[~2011-01-25 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 15:59 [PATCH 0/1] perf: hard-code NO_LIBPERL/NO_LIBPYTHO Bruce Ashfield
2011-01-25 15:59 ` [PATCH 1/1] linux-yocto/stable: " Bruce Ashfield
2011-01-25 17:20 ` Saul Wold [this message]
2011-01-25 18:42 ` [PATCH 0/1] " Bruce Ashfield
2011-01-28 1:32 ` Saul Wold
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=4D3F067A.2040103@intel.com \
--to=saul.wold@intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=poky@yoctoproject.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox