From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES
Date: Tue, 1 Mar 2011 18:51:39 -0600 [thread overview]
Message-ID: <4D6D949B.2020801@windriver.com> (raw)
In-Reply-To: <4D6D8BE8.9020907@mentor.com>
On 3/1/11 6:14 PM, Tom Rini wrote:
> On 03/01/2011 01:26 PM, Mark Hatle wrote:
>> On 3/1/11 1:55 PM, Koen Kooi wrote:
>>> ping
>>
>> Do you have an example showing how this is to be used?
>
> For example:
> http://cgit.openembedded.org/cgit.cgi/openembedded/tree/conf/machine/include/omap3.inc
> http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap3.inc
>
Thanks, that makes sense to me. I think it's useful. (It's already in, no
objections to that)
--Mark
next prev parent reply other threads:[~2011-03-02 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 19:21 [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES Koen Kooi
2011-03-01 19:55 ` Koen Kooi
2011-03-01 20:26 ` Mark Hatle
2011-03-02 0:14 ` Tom Rini
2011-03-02 0:51 ` Mark Hatle [this message]
2011-03-01 23:53 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2011-02-24 14:32 Koen Kooi
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=4D6D949B.2020801@windriver.com \
--to=mark.hatle@windriver.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