Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] [bug 1195] site/mips-common:	Cache	cvs_cv_func_printf_ptr
Date: Fri, 8 Jul 2011 14:55:09 -0700	[thread overview]
Message-ID: <4E177CBD.5060003@mentor.com> (raw)
In-Reply-To: <7A271CF8-4DB2-43E9-9FC2-860A9ACD3649@dominion.thruhere.net>

On 07/08/2011 01:49 PM, Koen Kooi wrote:
> I have a crude merged version of siteinfo.bbclass in meta-oe, any volunteers to have à look at the differences?

Ug, I didn't know oe-core was missing all of that.  Shoot it over to me,
I'll take a look Monday.

> 
> Op 8 jul. 2011 om 21:07 heeft "Zhang, Jessica" <jessica.zhang@intel.com> het volgende geschreven:
> 
>> We only have arm-common, common, ix86-common, mips-common, powerpc-common, sh-common under site, no Linux-common or glibc-common, and it's defined in all the arches-common files except mips-common.
>>
>> Thanks,
>> Jessica
>>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Tom Rini
>> Sent: Friday, July 08, 2011 11:37 AM
>> To: openembedded-core@lists.openembedded.org
>> Subject: Re: [OE-core] [PATCH 0/1] [bug 1195] site/mips-common: Cache cvs_cv_func_printf_ptr
>>
>> On 07/08/2011 09:31 AM, Richard Purdie wrote:
>>> On Thu, 2011-07-07 at 16:23 -0700, Jessica Zhang wrote:
>>>> The following changes since commit c412674cf818e77e35857fb93353e392e7ac9e53:
>>>>  Khem Raj (1):
>>>>        package.bbclass,prserv.bbclass: Compare USE_PR_SERV with "1" or "0"
>>>>
>>>> are available in the git repository at:
>>>>
>>>>  git://git.yoctoproject.org/poky-contrib jzhang/1195
>>>>  http://git.yoctoproject.org/cgit.cgi//log/?h=jzhang/1195
>>>>
>>>> Khem Raj (1):
>>>>  [bug 1195] site/mips-common: Cache cvs_cv_func_printf_ptr
>>>
>>> Merged to master, thanks.
>>
>> Late again and my fault this time but why is this in site/mips-common
>> and not site/linux-common or glibc-common?
>>
>> --
>> Tom Rini
>> Mentor Graphics Corporation
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


-- 
Tom Rini
Mentor Graphics Corporation



      reply	other threads:[~2011-07-08 21:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 23:23 [PATCH 0/1] [bug 1195] site/mips-common: Cache cvs_cv_func_printf_ptr Jessica Zhang
2011-07-07 23:23 ` [PATCH 1/1] " Jessica Zhang
2011-07-08 16:31 ` [PATCH 0/1] " Richard Purdie
2011-07-08 18:37   ` Tom Rini
2011-07-08 19:07     ` Zhang, Jessica
2011-07-08 20:49       ` Koen Kooi
2011-07-08 21:55         ` Tom Rini [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=4E177CBD.5060003@mentor.com \
    --to=tom_rini@mentor.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