From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] task-core-tools: Divide it into 3 recipes
Date: Tue, 31 Jan 2012 00:20:42 -0800 [thread overview]
Message-ID: <4F27A45A.4050106@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sp5UkNp_7fFmnUx-mBzbn7S5D_UHxQMR7DfcYQge2YVLw@mail.gmail.com>
On 01/30/2012 11:26 PM, Khem Raj wrote:
> On Mon, Jan 30, 2012 at 9:18 PM, Tom Zanussi<tom.zanussi@intel.com> wrote:
>> On Mon, 2012-01-30 at 20:19 -0800, Khem Raj wrote:
>>> On Mon, Jan 30, 2012 at 7:15 PM, Saul Wold<sgw@linux.intel.com> wrote:
>>>> This patch is going to require some coordination with meta-yocto and
>>>> possibly other layers that currently have .bbappends on the task-core-tools.
>>>>
>>>> It may be as simple as moving the dependency into this new -profile.bb task
>>>> file.
>>>>
>>>> I am going to hold this one for now.
>>>
>>> Are there other layers than meta-intel and meta-yocto that needs it.
>>> Please speak up. Can I request meta-yocto and meta-intel maintainers to please
>>> coordinate fixing the respective layers. Fix is that if you have been appending
>>
>> I've created a meta-intel branch ready to be pulled in when this is:
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/task-core-tools-rename
>
> thanks Tom. meta-yocto maintainer needs to fix
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/recipes-core/tasks/task-core-tools.bbappend
>
I will take care of this tomorrow, just wanted to make sure any other
places that needed it got the attention.
Sau!
>>
>> Tom
>>
>>
>> _______________________________________________
>> 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
>
next prev parent reply other threads:[~2012-01-31 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 4:39 [PATCH 0/5] Fix arm/tune-features for thumb instruction set Khem Raj
2012-01-27 4:39 ` [PATCH 1/5] gdb-common: Drop elfutils from DEPENDS Khem Raj
2012-01-27 4:39 ` [PATCH 2/5] task-core-tools: Divide it into 3 recipes Khem Raj
2012-01-31 3:15 ` Saul Wold
2012-01-31 4:19 ` Khem Raj
2012-01-31 5:18 ` Tom Zanussi
2012-01-31 7:26 ` Khem Raj
2012-01-31 8:20 ` Saul Wold [this message]
2012-01-27 4:39 ` [PATCH 3/5] arm/tune: Correct the logic which added thumb-interwork to OVERRIDES Khem Raj
2012-01-27 4:39 ` [PATCH 4/5] tunearch/arm: Differentiate between thumb code generation and thumb capability Khem Raj
2012-01-27 4:39 ` [PATCH 5/5] tune-thumb.inc: Delete Khem Raj
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=4F27A45A.4050106@linux.intel.com \
--to=sgw@linux.intel.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 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.