From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH 1/5] mfi-common: Break out set_hostos_runvars
Date: Wed, 20 Jul 2016 14:19:07 +0100 [thread overview]
Message-ID: <1469020751-12413-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
We are going to want to reuse this.
No functional change. (NB shell `local' variables have dynamic rather
than lexical scope.)
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
---
mfi-common | 16 ++++++++++++----
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git a/mfi-common b/mfi-common
index ca1e0dd..93cc3da 100644
--- a/mfi-common
+++ b/mfi-common
@@ -76,6 +76,17 @@ job_create_build () {
./cs-job-create $flight $job $recipe $global_runvars "$@"
}
+set_hostos_runvars () {
+ # caller should have done
+ # local hostos_runvars
+ # suite=....
+ # di_version=.... # perhaps
+ hostos_runvars="all_host_suite=$suite"
+ case "$di_version" in
+ ?*) hostos_runvars+=" all_host_di_version=$di_version"
+ esac
+}
+
create_build_jobs () {
local arch
@@ -414,10 +425,7 @@ test_matrix_iterate () {
;;
esac
- hostos_runvars="all_host_suite=$suite"
- case "$di_version" in
- ?*) hostos_runvars+=" all_host_di_version=$di_version"
- esac
+ set_hostos_runvars
for kern in ''; do
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-07-20 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 13:19 Ian Jackson [this message]
2016-07-20 13:19 ` [OSSTEST PATCH 2/5] mfi-common: Do not set di_version runvar to empty string in build jobs Ian Jackson
2016-07-20 13:19 ` [OSSTEST PATCH 3/5] cr-ensure-disk-space: Break out check_space Ian Jackson
2016-07-20 13:19 ` [OSSTEST PATCH 4/5] cr-ensure-disk-space: Run check_space before taking lock Ian Jackson
2016-07-20 13:19 ` [OSSTEST PATCH 5/5] mg-list-all-branches: Do not match ${BRANCHES+= ... } Ian Jackson
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=1469020751-12413-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).