Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 akuster808 <akuster808@gmail.com>,
	"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Adding new qemuppc64 machine config
Date: Tue, 09 Sep 2014 16:12:49 -0700	[thread overview]
Message-ID: <540F8971.6020803@gmail.com> (raw)
In-Reply-To: <1410274925.19272.44.camel@ted>



On 09/09/2014 08:02 AM, Richard Purdie wrote:
> On Mon, 2014-09-08 at 22:03 -0700, akuster808 wrote:
>> I forgot to mention. I will update linux-yocto_3.1x.bb too.
>
> You need to talk to Bruce about that. I'm also worried about this coming
> in this late, after feature freeze.

I wasn't targeting getting it in for 1.7.

I am just passing along it along so maybe someone else might gain some 
benefit from it.


- Armin

>
> Cheers,
>
> Richard
>
>> - Armin
>>
>> On 09/08/2014 06:53 PM, Armin Kuster wrote:
>>> apply after "linux-yocto/3.14: configuration updates and feature merges."
>>>
>>>
>>> Armin Kuster (1):
>>>     qemuppc64: add machine
>>>
>>>    meta/conf/machine/qemuppc64.conf | 16 ++++++++++++++++
>>>    1 file changed, 16 insertions(+)
>>>    create mode 100644 meta/conf/machine/qemuppc64.conf
>>>
>
>


      reply	other threads:[~2014-09-09 23:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  1:53 [PATCH] Adding new qemuppc64 machine config Armin Kuster
2014-09-09  1:53 ` [[PATCH] qemuppc64: add machine Armin Kuster
2014-09-09  8:05   ` Richard Purdie
2014-09-09 14:46     ` Mark Hatle
2014-09-09 15:13       ` akuster808
2014-09-09 15:03     ` akuster808
2014-09-11  2:41     ` akuster808
2014-09-09  5:03 ` [PATCH] Adding new qemuppc64 machine config akuster808
2014-09-09 15:02   ` Richard Purdie
2014-09-09 23:12     ` akuster808 [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=540F8971.6020803@gmail.com \
    --to=akuster808@gmail.com \
    --cc=Bruce.Ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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