From: Joshua Lock <joshuagloe@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] Python3 runqemu
Date: Mon, 5 Sep 2016 21:32:54 +0100 [thread overview]
Message-ID: <cover.1473107499.git.joshua.g.lock@intel.com> (raw)
This small series against master-next (as the python3 runqemu hasn't made it to
master yet) fixes the new runqemu for a workflow of mine where I build on a
headless machine and copy images locally to test them with runqemu.
Changes since v1:
* drop a patch to replace an ls -t call with Python's glob()
* Fix and enhance reading STAGING_*_NATIVE from the bitbake environment, tested
with artefacts in a completely different path to the build path and invoking
with both the qemuboot.conf file as the arg to runqemu and the parent
directory.
The following changes since commit 5b3ac3cd92d1f021c06b22eaa0e74ab8dfb22764:
kernel-module-split.bbclass: no need for running depmod (2016-09-05 17:45:53 +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 (3):
runqemu: fix typos
runqemu: assume artefacts are relative to *.qemuboot.conf
runqemu: better handle running on a host with different paths
scripts/runqemu | 57 ++++++++++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 54 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-05 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 20:32 Joshua Lock [this message]
2016-09-05 20:32 ` [PATCH v2 1/3] runqemu: fix typos Joshua Lock
2016-09-05 20:32 ` [PATCH v2 2/3] runqemu: assume artefacts are relative to *.qemuboot.conf Joshua Lock
2016-09-05 20:32 ` [PATCH v2 3/3] runqemu: better handle running on a host with different paths Joshua Lock
2016-09-06 6:11 ` [PATCH v2 0/3] Python3 runqemu Robert Yang
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.1473107499.git.joshua.g.lock@intel.com \
--to=joshuagloe@gmail.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