From: Saul Wold <sgw@linux.intel.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/5] Add support for PowerPC e500v2/SPE
Date: Tue, 19 Jul 2011 08:42:52 -0700 [thread overview]
Message-ID: <4E25A5FC.6080504@linux.intel.com> (raw)
In-Reply-To: <7F6E9823-395B-4AEC-8874-A56C3A098DC4@kernel.crashing.org>
On 07/19/2011 08:40 AM, Kumar Gala wrote:
>
> On Jul 19, 2011, at 10:32 AM, Saul Wold wrote:
>
>> On 07/19/2011 06:17 AM, Kumar Gala wrote:
>>>
>>> On Jul 19, 2011, at 2:44 AM, Koen Kooi wrote:
>>>
>>>>
>>>> Op 19 jul 2011, om 07:21 heeft Kumar Gala het volgende geschreven:
>>>>
>>>>> The majority of support for the PowerPC e500v2/SPE target already
>>>>> exists. However some minor cleans are required to get things working
>>>>> completely.
>>>>>
>>>>> The e500v2 utilizes a unique floating point programming model / ABI from
>>>>> other PowerPC targets and thus requires special handling.
>>>>
>>>>
>>>> These should be sent to the oe-core list against the oe-core tree, not the poky list against the poky tree
>>>
>>> Will do so, it was unclear to me how patches go from oe-core to/from yocto.
>>>
>> Kumar,
>>
>> If it goes into the meta/recipes or meta/conf area then it goes to oe-core, if the patch is the PPC machine-specific and changes are in meta-yocto, then it should go to the yocto ml.
>>
>> As mentioned above, all these patches should go to oe-core
>>
>> I hope that clears things up.
>>
>> Sau!
>
> Its a start, how to things go from oe-core git to yocto git?
>
Richard Purdie the maintainer for both has a process he uses to merge
changes from oe-core to yocto. Anything in oe-core will be merged into
yocto's meta directory.
Sau!
> - k
prev parent reply other threads:[~2011-07-19 15:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 5:21 [PATCH 0/5] Add support for PowerPC e500v2/SPE Kumar Gala
2011-07-19 5:21 ` [PATCH 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Kumar Gala
2011-07-19 5:21 ` [PATCH 2/5] tclibc-*glibc: Utilize TARGET_FPU for gnuspe setting Kumar Gala
2011-07-19 5:21 ` [PATCH 3/5] tune-ppce500v2: Add a tune file for PowerPC e500v2 cores Kumar Gala
2011-07-19 5:21 ` [PATCH 4/5] openssl: Add handling for linux-gnuspe-powerpc Kumar Gala
2011-07-19 5:21 ` [PATCH 5/5] flac: fix build issues with e500v2 (gnuspe) toolchain Kumar Gala
2011-07-19 6:01 ` [PATCH 3/5] tune-ppce500v2: Add a tune file for PowerPC e500v2 cores Khem Raj
2011-07-19 6:25 ` Kumar Gala
2011-07-19 6:08 ` [PATCH 2/5] tclibc-*glibc: Utilize TARGET_FPU for gnuspe setting Khem Raj
2011-07-19 6:28 ` Kumar Gala
2011-07-19 6:04 ` [PATCH 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Khem Raj
2011-07-19 6:47 ` Kumar Gala
2011-07-19 14:07 ` [yocto] " Kumar Gala
2011-07-19 14:07 ` Kumar Gala
2011-07-19 14:41 ` Trying to create OpenDDS recipe Ourada, Paul
2011-07-28 21:48 ` Darren Hart
2011-07-28 23:16 ` Ourada, Paul
2011-07-29 0:00 ` Darren Hart
2011-07-19 15:02 ` [PATCH 1/5] gcc: Add gcc configure for PowerPC e500v2/SPE embedded floating point ABI Khem Raj
2011-07-19 6:00 ` [PATCH 0/5] Add support for PowerPC e500v2/SPE Khem Raj
2011-07-19 7:44 ` Koen Kooi
2011-07-19 13:17 ` Kumar Gala
2011-07-19 15:32 ` Saul Wold
2011-07-19 15:40 ` Kumar Gala
2011-07-19 15:42 ` 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=4E25A5FC.6080504@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=galak@kernel.crashing.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 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.