From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: [OSSTEST PATCH v2 3/4] ts-xen-build: Enable CONFIG_EXPERT
Date: Tue, 8 Nov 2016 15:09:46 +0000 [thread overview]
Message-ID: <1478617787-20713-3-git-send-email-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <1478617787-20713-1-git-send-email-ian.jackson@eu.citrix.com>
This requires an environment variable set in the build environment,
too. (There is an argument amongst hypervisor maintainers about
whether this requirement in xen.git is a good idea; but, nevertheless,
it is currently there in several existing trees, so we need to set
it.)
Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
CC: Andrew Cooper <andrew.cooper3@citrix.com>
---
ts-xen-build | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/ts-xen-build b/ts-xen-build
index 3e53d74..80f6492 100755
--- a/ts-xen-build
+++ b/ts-xen-build
@@ -43,6 +43,10 @@ builddirsprops();
my $enable_xsm = ($r{enable_xsm}//'false') =~ m/true/ ? 1 : 0;
+$buildcmd_global_prefix= <<END;
+ export XEN_CONFIG_EXPERT=y
+END
+
sub config_tree ($$$) {
my ($which, $configurlvar, $configtagvar) = @_;
@@ -103,6 +107,7 @@ END
END
<<END
if test -f xen/Kconfig; then
+ echo >>xen/.config CONFIG_EXPERT=y
echo >>xen/.config CONFIG_HVM_FEP=y
fi
END
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-11-08 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 15:09 [OSSTEST PATCH v2 1/4] xtf: Always boot with loglvl=all guest_loglvl=all Ian Jackson
2016-11-08 15:09 ` [OSSTEST PATCH v2 2/4] BuildSupport: Honour $buildcmd_global_prefix Ian Jackson
2016-11-08 15:09 ` Ian Jackson [this message]
2016-11-08 15:09 ` [OSSTEST PATCH v2 4/4] ts-xen-build: Enable CONFIG_VERBOSE_DEBUG Ian Jackson
2016-11-08 15:18 ` Andrew Cooper
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=1478617787-20713-3-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=andrew.cooper3@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).