From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: [PATCH] meta-selftest: Add qemux86copy machine
Date: Wed, 30 Sep 2015 14:47:13 +0100 [thread overview]
Message-ID: <1443620833.5162.83.camel@linuxfoundation.org> (raw)
I know Martin finds something like this useful for testing sstate signatures,
this adds one to meta-selftest so we can use it from oe-selftest in the sstate
tests there too.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
diff --git a/meta-selftest/conf/machine/qemux86copy.conf b/meta-selftest/conf/machine/qemux86copy.conf
new file mode 100644
index 0000000..bcce2f5
--- /dev/null
+++ b/meta-selftest/conf/machine/qemux86copy.conf
@@ -0,0 +1,3 @@
+require conf/machine/qemux86.conf
+
+MACHINEOVERRIDES .= ":qemux86"
next reply other threads:[~2015-09-30 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:47 Richard Purdie [this message]
2015-09-30 14:28 ` [PATCH] meta-selftest: Add qemux86copy machine Martin Jansa
2015-09-30 15:59 ` Richard Purdie
2015-09-30 16:19 ` Martin Jansa
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=1443620833.5162.83.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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