All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: xen-devel@lists.xen.org
Cc: Doug Goldstein <cardoe@cardoe.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: [OSSTEST PATCH v3] support XSM/FLASK via Kconfig
Date: Wed,  6 Jan 2016 13:19:54 -0600	[thread overview]
Message-ID: <1452107994-2681-1-git-send-email-cardoe@cardoe.com> (raw)

In antcipation of XSM and FLASK migrating to Kconfig add support for
building them via Kconfig or the existing mechanism.

Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
---
Still untested but visually looks correct.

Changes since v3:
- Wrap all hunks of code with checks for Kconfig to not dirty the tree

Changes since v2:
- Support Xen versions prior to Kconfig being integrated
---
 ts-xen-build | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/ts-xen-build b/ts-xen-build
index 80b1faa..bc4e41a 100755
--- a/ts-xen-build
+++ b/ts-xen-build
@@ -55,6 +55,10 @@ sub checkout () {
 	echo >>.config KERNELS=''
 END
                (nonempty($r{enable_xsm}) ? <<END : '').
+	if test -f xen/Kconfig; then
+		echo >>xen/.config CONFIG_XSM='${build_xsm}'
+		echo >>xen/.config CONFIG_FLASK='${build_xsm}'
+	fi
 	echo >>.config XSM_ENABLE='${build_xsm}'
 END
                (nonempty($r{tree_qemu}) ? <<END : '').
@@ -126,6 +130,9 @@ END
 END
 #/;
     buildcmd_stamped_logged(9000, 'build', '',<<END,'');
+            if test -f xen/Kconfig; then
+                $make_prefix make -C xen olddefconfig
+            fi
             $make_prefix make $makeflags @ARGV
 END
 
-- 
2.4.10

             reply	other threads:[~2016-01-06 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 19:19 Doug Goldstein [this message]
2016-01-07 10:04 ` [OSSTEST PATCH v3] support XSM/FLASK via Kconfig Ian Campbell
2016-01-07 15:37   ` Doug Goldstein
2016-01-08 16:29 ` 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=1452107994-2681-1-git-send-email-cardoe@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.