All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 0/1] linux-yocto: temporary NO_LIBPERL fix for perf
Date: Fri, 14 Jan 2011 20:14:39 -0800	[thread overview]
Message-ID: <4D311F2F.8000104@intel.com> (raw)
In-Reply-To: <AANLkTim3ES1fWfpbkvUrQ-ynHFedKCL0T8RmkAwEsB5a@mail.gmail.com>

On 01/14/2011 07:56 PM, Bruce Ashfield wrote:
> On Fri, Jan 14, 2011 at 10:43 PM, Tom Zanussi<tom.zanussi@intel.com>  wrote:
>> On Fri, 2011-01-14 at 18:46 -0800, Bruce Ashfield wrote:
>>> On Fri, Jan 14, 2011 at 5:49 PM, Tom Zanussi<tom.zanussi@intel.com>  wrote:
>>>> I'm not familiar enough with the perf recipe to come up with a proper
>>>> fix for the problem yet, but this patch at least removes the build
>>>> error that recently started happening with the linux-yocto perf
>>>> compile.
>>>>
>>>> I'll send a patch re-instating the code it removes once I've
>>>> understood the perf recipe and root-caused the problem.  In any case,
>>>> it doesn't remove any functionality that was there before - NO_LIBPERL
>>>> was always the case, but the code that made that happen just started
>>>> blowing up for some reason.
>>>
>>>
>>> Thanks Tom! I was going to offer to merge this into the kernel
>>> tree itself, since having external patches to the repo isn't something
>>> we typically do. But in this case, the patch is temporary so I'm going
>>> to just ack it, and stay out of the way.
>>>
>>
>> Hi Bruce,
>>
>> The funny thing is that my first inclination and preference was to just
>> submit the kernel patch, and I was about to do that anyway after having
>> initial trouble getting it to apply this way...  Anyway, I decided at
>> least this way if you weren't around to apply it to the kernel tree,
>> Saul was waiting for it and it would be applied regardless - next time
>> I'll just do it the easy way ;-)
>
> Agreed.  We think alike on this one. Hedging your bets on the one
> step process of Saul pulling it into master without me needing to
> be in the middle was good, but given the choice, I'd chose the merge
> to the kernel branches as well.
>
The question still remains, is the root cause of this issue after the 
perl update, so Nitin is still looking into this.

Thanks for working the patch out so quickly, there are still a couple of 
issues with Master, but it's looking alot better right now!

Sau!

> Cheers,
>
> Bruce
>
>>
>> Tom
>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> Pull URL: git://git.pokylinux.org/poky-contrib.git
>>>>   Branch: tzanussi/perf-no-libperl-fix
>>>>   Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tzanussi/perf-no-libperl-fix
>>>>
>>>> Thanks,
>>>>     Tom Zanussi<tom.zanussi@intel.com>
>>>> ---
>>>>
>>>>
>>>> Tom Zanussi (1):
>>>>   linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON
>>>>
>>>>   .../linux-yocto/tools-perf-no-scripting.patch      |   49 ++++++++++++++++++++
>>>>   meta/recipes-kernel/linux/linux-yocto_git.bb       |    5 +-
>>>>   2 files changed, 52 insertions(+), 2 deletions(-)
>>>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto/tools-perf-no-scripting.patch
>>>>
>>>> _______________________________________________
>>>> poky mailing list
>>>> poky@yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/poky
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>



      reply	other threads:[~2011-01-15  4:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 22:49 [PATCH 0/1] linux-yocto: temporary NO_LIBPERL fix for perf Tom Zanussi
2011-01-14 22:49 ` [PATCH 1/1] linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON Tom Zanussi
2011-01-15  2:46 ` [PATCH 0/1] linux-yocto: temporary NO_LIBPERL fix for perf Bruce Ashfield
2011-01-15  3:43   ` Tom Zanussi
2011-01-15  3:56     ` Bruce Ashfield
2011-01-15  4:14       ` Saul Wold [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=4D311F2F.8000104@intel.com \
    --to=saul.wold@intel.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=poky@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.