From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][RFC] conf/machine/include/arm add extra MACHINEOVERRIDES like x86 does
Date: Tue, 13 Dec 2011 12:31:10 +0000 [thread overview]
Message-ID: <1323779470.2731.66.camel@ted> (raw)
In-Reply-To: <1323281084-30590-1-git-send-email-Martin.Jansa@gmail.com>
On Wed, 2011-12-07 at 19:04 +0100, Martin Jansa wrote:
> * motivated by this NAK
> http://patchwork.openembedded.org/patch/15777/
> and today's discussion on #yocto I hope it's worth it to send this RFC
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/conf/machine/include/arm/arch-armv4.inc | 1 +
> meta/conf/machine/include/arm/arch-armv5.inc | 1 +
> meta/conf/machine/include/arm/arch-armv6.inc | 1 +
> meta/conf/machine/include/arm/arch-armv7.inc | 1 +
> meta/conf/machine/include/arm/arch-armv7a.inc | 1 +
> 5 files changed, 5 insertions(+), 0 deletions(-)
Merged to master, thanks.
I assume you'll follow up and tweak the overrides in OE-Core to match
this?
Cheers,
Richard
next prev parent reply other threads:[~2011-12-13 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 18:04 [PATCH][RFC] conf/machine/include/arm add extra MACHINEOVERRIDES like x86 does Martin Jansa
2011-12-08 15:48 ` Martin Jansa
2011-12-13 20:01 ` Khem Raj
2011-12-15 9:29 ` Koen Kooi
2011-12-15 13:06 ` Martin Jansa
2011-12-15 15:03 ` Koen Kooi
2011-12-13 8:10 ` Martin Jansa
2011-12-13 12:31 ` Richard Purdie [this message]
2011-12-13 13:59 ` [PATCH][oe-core 0/3] PR bumps and arm OVERRIDE fix Martin Jansa
2011-12-13 13:59 ` [PATCH][oe-core 1/3] qt4: use armv6 override instead of armv6-vfp Martin Jansa
2011-12-13 13:59 ` [PATCH][oe-core 2/3] xf86-video-omapfb: bump PR due to arm OVERRIDES change Martin Jansa
2011-12-13 13:59 ` [PATCH][oe-core 3/3] python: " Martin Jansa
2011-12-13 15:06 ` [PATCH][oe-core 0/3] PR bumps and arm OVERRIDE fix Richard Purdie
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=1323779470.2731.66.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.