Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	<openembedded-core@lists.openembedded.org>
Subject: V2 Re: [PATCH 0/7] fixes for runqemu
Date: Mon, 21 Mar 2016 17:58:22 +0800	[thread overview]
Message-ID: <56EFC5BE.4070906@windriver.com> (raw)
In-Reply-To: <56EF5420.7030809@windriver.com>



On 03/21/2016 09:53 AM, Robert Yang wrote:
>
>
> On 03/21/2016 06:40 AM, Richard Purdie wrote:
>> On Sun, 2016-03-13 at 23:52 -0700, Robert Yang wrote:
>>> The following changes since commit
>>> 9d5fa6da5ae14b26a83ec1af609d4c45944bfd44:
>>>
>>>    cross-canadian/libgcc: fix aarch64's multilib SDK (2016-03-13
>>> 19:36:57 -0700)
>>>
>>> are available in the git repository at:
>>>
>>>    git://git.openembedded.org/openembedded-core-contrib rbt/runqemu
>>>    http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log
>>> /?h=rbt/runqemu
>>>
>>> Robert Yang (7):
>>>    runqemu: fix ROOTFS for vmdk
>>>    runqemu: simplify the checking for vm images
>>>    runqemu: remove ISO and RAMFS from help text
>>>    runqemu: add support for qcow2 and vdi
>>>    runqemu: simplify checking for iso and ramfs
>>>    runqemu-internal: cleanup unsed code
>>>    runqemu-internal: split the code into functions
>>
>> I have a feeling one of these causes:
>>
>> https://autobuilder.yoctoproject.org/main/builders/nightly-oe-selftest/
>> builds/426/steps/Running%20oe-selftest/logs/stdio
>>
>> (the  test_qemu (oeqa.selftest.wic.Wic) failure)
>
> Sorry, I will fix it.

I updated the patches in the repo, now:
$ oe-selftest -r wic.Wic.test_qemu
and
$ oe-selftest -r wic.Wic.test_qemux86_directdisk

Work well.

* Changes of V2:
- Update "runqemu: fix ROOTFS for vmdk", check for ide/scsi drive, if not
   found, then use virtio block drive.


   git://git.openembedded.org/openembedded-core-contrib rbt/runqemu
   http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/rpm

Robert Yang (7):
   runqemu: fix ROOTFS for vmdk
   runqemu: simplify the checking for vm images
   runqemu: remove ISO and RAMFS from help text
   runqemu: add support for qcow2 and vdi
   runqemu: simplify checking for iso and ramfs
   runqemu-internal: cleanup unsed code
   runqemu-internal: split the code into functions

// Robert

>
> // Robert
>
>>
>> Cheers,
>>
>> Richard
>>


      reply	other threads:[~2016-03-21  9:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14  6:52 [PATCH 0/7] fixes for runqemu Robert Yang
2016-03-14  6:52 ` [PATCH 1/7] runqemu: fix ROOTFS for vmdk Robert Yang
2016-03-14  6:52 ` [PATCH 2/7] runqemu: simplify the checking for vm images Robert Yang
2016-03-14  6:52 ` [PATCH 3/7] runqemu: remove ISO and RAMFS from help text Robert Yang
2016-03-14  6:52 ` [PATCH 4/7] runqemu: add support for qcow2 and vdi Robert Yang
2016-03-14  6:52 ` [PATCH 5/7] runqemu: simplify checking for iso and ramfs Robert Yang
2016-03-14  6:52 ` [PATCH 6/7] runqemu-internal: cleanup unsed code Robert Yang
2016-03-14  6:52 ` [PATCH 7/7] runqemu-internal: split the code into functions Robert Yang
2016-03-20 22:40 ` [PATCH 0/7] fixes for runqemu Richard Purdie
2016-03-21  1:53   ` Robert Yang
2016-03-21  9:58     ` 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=56EFC5BE.4070906@windriver.com \
    --to=liezhi.yang@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