From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] runqemu fixes
Date: Fri, 16 Sep 2016 13:52:27 +0100 [thread overview]
Message-ID: <cover.1474030160.git.joshua.g.lock@intel.com> (raw)
This series includes several fixes and enhancements for runqemu to better align
with the previous shell based implementation.
The following changes since commit 059d475b6bce1e5414170a4fe2e7989f6b0eacd6:
oeqa/utils/decorators: LogResults fix race condition in linkfile (2016-09-15 12:14:40 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib joshuagl/runqemu
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=joshuagl/runqemu
Joshua Lock (6):
runqemu: add guidance to resolve issues with missing files
qemuboot: write the full kernel filename, not the link name
runqemu: clarify an INFO message
qemuboot: also write the kernel link name to the conf file
runqemu: try symlinks when kernel or rootfs can't be found
runqemu: work even if a *.qemuboot.conf isn't found
meta/classes/qemuboot.bbclass | 13 +++++++++++--
scripts/runqemu | 43 ++++++++++++++++++++++++++++++++++++-------
2 files changed, 47 insertions(+), 9 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-16 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 12:52 Joshua Lock [this message]
2016-09-16 12:52 ` [PATCH 1/6] runqemu: add guidance to resolve issues with missing files Joshua Lock
2016-09-16 12:52 ` [PATCH 2/6] qemuboot: write the full kernel filename, not the link name Joshua Lock
2016-09-16 12:52 ` [PATCH 3/6] runqemu: clarify an INFO message Joshua Lock
2016-09-16 12:52 ` [PATCH 4/6] qemuboot: also write the kernel link name to the conf file Joshua Lock
2016-09-16 12:52 ` [PATCH 5/6] runqemu: try symlinks when kernel or rootfs can't be found Joshua Lock
2016-09-18 7:23 ` Robert Yang
2016-09-16 12:52 ` [PATCH 6/6] runqemu: work even if a *.qemuboot.conf isn't found Joshua Lock
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=cover.1474030160.git.joshua.g.lock@intel.com \
--to=joshua.g.lock@intel.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