From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Randle, William C" <william.c.randle@intel.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V5 00/10] runqemu: refactor it and remove machine knowledge
Date: Wed, 31 Aug 2016 09:08:40 +0800 [thread overview]
Message-ID: <fda8f2b2-dcb4-40e6-54ba-8fd3aa81e633@windriver.com> (raw)
In-Reply-To: <1472598098.29583.61.camel@linuxfoundation.org>
On 08/31/2016 07:01 AM, Richard Purdie wrote:
> On Thu, 2016-08-25 at 21:59 +0000, Randle, William C wrote:
>> On Thu, 2016-08-25 at 22:45 +0100, Burton, Ross wrote:
>>> Hi Robert,
>>>
>>> So close! qemuarm64 is breaking on the AB:
>>>
>>> https://autobuilder.yoctoproject.org/main/builders/nightly-arm64/bu
>>> ilds/536/steps/Running%20Sanity%20Tests/logs/stdio
>>>
>>> I suspect we're passing some options to runqemu that you didn't
>>> cover in your testing.
>>>
>>> Ross
>>>
>> It looks like it's just a missing space between the -m arg and
>> -device:
>> -m 512-device
>
> I added an attempt at a fix for this into -next FWIW
Thanks, I had fixed this in the repo, and the fix is the same as RP's,
I should reply to this thread, too, but sorry I replied to another thread:
Re: [OE-core] [PATCH V4 00/11] runqemu: refactor it and remove machine knowledge
// Robert
>
> Cheers,
>
> Richard
>
prev parent reply other threads:[~2016-08-31 1:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 14:40 [PATCH V5 00/10] runqemu: refactor it and remove machine knowledge Robert Yang
2016-08-25 14:40 ` [PATCH V5 01/10] qemuboot.bbclass: add it for runqemu Robert Yang
2016-08-25 14:40 ` [PATCH V5 02/10] qemuarm.conf: set vars " Robert Yang
2016-08-25 14:41 ` [PATCH V5 03/10] qemuarm64.conf: " Robert Yang
2016-08-25 14:41 ` [PATCH V5 04/10] qemux86.conf/qemux86-64.conf: " Robert Yang
2016-08-25 14:41 ` [PATCH V5 05/10] qemumips/qemumips64.conf: " Robert Yang
2016-08-25 14:41 ` [PATCH V5 06/10] qemuppc.conf: " Robert Yang
2016-08-25 14:41 ` [PATCH V5 07/10] qemu.inc: inherit qemuboot.bbclass Robert Yang
2016-08-25 14:41 ` [PATCH V5 08/10] runqemu: refactor it and remove machine knowledge Robert Yang
2016-08-25 14:41 ` [PATCH V5 09/10] nativesdk-qemu-helper: fix for new runqemu Robert Yang
2016-08-25 14:41 ` [PATCH V5 10/10] qemurunner.py/qemutinyrunner.py: remove runqemu-internal Robert Yang
2016-08-25 21:45 ` [PATCH V5 00/10] runqemu: refactor it and remove machine knowledge Burton, Ross
2016-08-25 21:59 ` Randle, William C
2016-08-30 23:01 ` Richard Purdie
2016-08-31 1:08 ` Robert Yang [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=fda8f2b2-dcb4-40e6-54ba-8fd3aa81e633@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.com \
--cc=william.c.randle@intel.com \
/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