From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mx1.pokylinux.org (Postfix) with ESMTP id 2C4F24C800A3 for ; Tue, 19 Jul 2011 10:42:53 -0500 (CDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 19 Jul 2011 08:42:52 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,229,1309762800"; d="scan'208";a="29791348" Received: from unknown (HELO [10.255.13.254]) ([10.255.13.254]) by fmsmga002.fm.intel.com with ESMTP; 19 Jul 2011 08:42:52 -0700 Message-ID: <4E25A5FC.6080504@linux.intel.com> Date: Tue, 19 Jul 2011 08:42:52 -0700 From: Saul Wold User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc13 Thunderbird/3.1.10 MIME-Version: 1.0 To: Kumar Gala References: <1311052872-10569-1-git-send-email-galak@kernel.crashing.org> <9C2FF9D1-726F-45C2-A22B-DF4E07D48809@kernel.crashing.org> <4E25A374.5010108@linux.intel.com> <7F6E9823-395B-4AEC-8874-A56C3A098DC4@kernel.crashing.org> In-Reply-To: <7F6E9823-395B-4AEC-8874-A56C3A098DC4@kernel.crashing.org> Cc: yocto@yoctoproject.org Subject: Re: [PATCH 0/5] Add support for PowerPC e500v2/SPE X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jul 2011 15:42:53 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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