From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH] soc-family.inc: to be included in machine.conf to add SOC_FAMILY to MACHINEOVERRIDE
Date: Sun, 04 Mar 2012 04:49:53 -0800 [thread overview]
Message-ID: <1330865393.7590.0.camel@ted> (raw)
In-Reply-To: <1330842274-13635-1-git-send-email-denis@denix.org>
On Sun, 2012-03-04 at 01:24 -0500, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@ti.com>
>
> Add a soc-family.inc file that can be included in a machine.conf to enable
> the use of SOC_FAMILY in MACHINEOVERRIDE, which could be useful to group
> multiple machines with the same common base. Some examples can be seen in
> meta-ti BSP layer.
>
> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> ---
> meta/conf/machine/include/soc-family.inc | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
> create mode 100644 meta/conf/machine/include/soc-family.inc
Merged to maser, thanks.
Richard
prev parent reply other threads:[~2012-03-04 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 6:24 [PATCH] soc-family.inc: to be included in machine.conf to add SOC_FAMILY to MACHINEOVERRIDE Denys Dmytriyenko
2012-03-04 12:49 ` Richard Purdie [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=1330865393.7590.0.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=denys@ti.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