From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: tom.zanussi@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/6] meta-intel: add a couple common .inc files
Date: Fri, 15 Jul 2011 14:23:30 +0100 [thread overview]
Message-ID: <1310736210.20015.1225.camel@rex> (raw)
In-Reply-To: <f69321f9d19943ec1815681e6568524387cfe5c0.1310689271.git.tom.zanussi@intel.com>
Hi Tom,
On Thu, 2011-07-14 at 19:55 -0500, tom.zanussi@intel.com wrote:
> From: Tom Zanussi <tom.zanussi@intel.com>
>
> The meta-intel BSPs currently have a number of machine settings common
> to all - factor these out into a couple common include files.
For reference common include files are usually placed in
conf/machine/include/. If that happens they also need non-generic
suitably namespaced names, likely including "x86" or "ia32" in this
case.
The benefit is you can then refer to one of these includes from another
layer.
It also means you can refer to them as:
include conf/machine/includes/xxx
in other conf files removing some of the potential path issues.
I do like the cleanup this gives though, this is just a detail! :)
Cheers,
Richard
next prev parent reply other threads:[~2011-07-15 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 0:55 [PATCH 0/6] factor out some common meta-intel settings tom.zanussi
2011-07-15 0:55 ` [PATCH 1/6] meta-intel: add a couple common .inc files tom.zanussi
2011-07-15 13:23 ` Richard Purdie [this message]
2011-07-15 13:36 ` Tom Zanussi
2011-07-15 18:30 ` Darren Hart
2011-07-15 0:55 ` [PATCH 2/6] meta-sugarbay: use " tom.zanussi
2011-07-15 0:55 ` [PATCH 3/6] meta-crownbay: " tom.zanussi
2011-07-15 0:55 ` [PATCH 4/6] meta-fishriver: " tom.zanussi
2011-07-15 0:55 ` [PATCH 5/6] meta-jasperforest: " tom.zanussi
2011-07-15 0:55 ` [PATCH 6/6] meta-emenlow: " tom.zanussi
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=1310736210.20015.1225.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=tom.zanussi@intel.com \
--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.