public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Joshua Lock <joshua.g.lock@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] runqemu: fix run from testimage with non-standard DEPLOY_DIR_IMAGE
Date: Thu,  8 Sep 2016 21:49:12 +0100	[thread overview]
Message-ID: <cover.1473367495.git.joshua.g.lock@intel.com> (raw)

Note: This patch is against master-next, as the Python 3 runqemu hasn't made it
to master yet.

This fixes a workflow where the contents of DEPLOY_DIR_IMAGE are copied to a
user-created directory which doesn't follow the standard OE naming of 
DEPLOY_DIR_IMAGE and then DEPLOY_DIR_IMAGE is set to point at that directory in
local.conf

Per the commit message it's possible that we don't want to try and check the
value a user uses for MACHINE and just let runqemu fail later, but this change
fixes the mentioned workflow without changing too much of the runqemu behaviour.


The following changes since commit 958c05bfa1009c57d8acc45ea0ed4b7f6f0d377a:

  maintainers.inc: rename gtk-doc-stub to gtk-doc, reassign to me (2016-09-08 17:05:37 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib joshuagl/runqemu
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=joshuagl/runqemu

Joshua Lock (1):
  runqemu: fix run from testimage with non-standard DEPLOY_DIR_IMAGE

 scripts/runqemu | 13 +++++++++++++
 1 file changed, 13 insertions(+)

-- 
2.7.4


             reply	other threads:[~2016-09-08 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 20:49 Joshua Lock [this message]
2016-09-08 20:49 ` [PATCH 1/1] runqemu: fix run from testimage with non-standard DEPLOY_DIR_IMAGE 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.1473367495.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