xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: ian.jackson@eu.citrix.com, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [OSSTEST PATCH] Drop build-*-oldkern
Date: Mon, 12 Jun 2017 12:31:45 +0100	[thread overview]
Message-ID: <20170612113145.7ncge5hqikkompgi@citrix.com> (raw)
In-Reply-To: <20170612112636.26613-1-wei.liu2@citrix.com>

And the runvar changes:

--- ../osstest-master-runvars   2017-06-06 14:38:00.480138417 +0100
+++ ../osstest-new-runvars      2017-06-06 14:41:24.134725010 +0100
-xen-unstable               build-amd64-oldkern                                   all_host_di_version     current
-xen-unstable               build-amd64-oldkern                                   all_host_suite          wheezy
-xen-unstable               build-amd64-oldkern                                   arch                    amd64
-xen-unstable               build-amd64-oldkern                                   build_lvextend_max      50
-xen-unstable               build-amd64-oldkern                                   host_hostflags          share-build-wheezy-amd64,arch-amd64,suite-wheezy,pur
-xen-unstable               build-amd64-oldkern                                   kconfighow              create-config-sh
-xen-unstable               build-amd64-oldkern                                   kimagefile              vmlinux
-xen-unstable               build-amd64-oldkern                                   revision_linux
-xen-unstable               build-amd64-oldkern                                   tree_linux              http://xenbits.xen.org/linux-2.6.18-xen.hg
-xen-unstable               build-i386-oldkern                                    all_host_di_version     current
-xen-unstable               build-i386-oldkern                                    all_host_suite          wheezy
-xen-unstable               build-i386-oldkern                                    arch                    i386
-xen-unstable               build-i386-oldkern                                    build_lvextend_max      50
-xen-unstable               build-i386-oldkern                                    host_hostflags          share-build-wheezy-i386,arch-i386,suite-wheezy,purpo
-xen-unstable               build-i386-oldkern                                    kconfighow              create-config-sh
-xen-unstable               build-i386-oldkern                                    kimagefile              vmlinux
-xen-unstable               build-i386-oldkern                                    revision_linux
-xen-unstable               build-i386-oldkern                                    tree_linux              http://xenbits.xen.org/linux-2.6.18-xen.hg


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-06-12 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 11:26 [OSSTEST PATCH] Drop build-*-oldkern Wei Liu
2017-06-12 11:31 ` Wei Liu [this message]
2017-06-12 13:31   ` [OSSTEST PATCH] Drop build-*-oldkern [and 1 more messages] 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=20170612113145.7ncge5hqikkompgi@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=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).