From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xenproject.org
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [OSSTEST PATCH 2/2] mfi-common: Enable livepatch tests in 4.10 and 4.11 as intended (!)
Date: Thu, 1 Nov 2018 15:58:07 +0000 [thread overview]
Message-ID: <1aefcd8a-698e-c88f-b381-aade8aef6bef@citrix.com> (raw)
In-Reply-To: <20181101155335.20138-2-ian.jackson@eu.citrix.com>
On 01/11/18 15:53, Ian Jackson wrote:
> The pattern xen-4.1* matches xen-4.10-testing, xen-4.11-testing, etc.
> The right approach is to state the excluded branch names explicitly
> as is done elsewhere.
>
> Resulting changes (standalone-generate-dump-flight-runvars):
> * new jobs: test-amd64-{amd64,i386}-livepatch
> * runvar set: enable_livepatch=true in build-ARCH, build-ARCH-xsm
> * all of the above in branches: xen-4.10-testing xen-4.11-testing
>
> Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> CC: Andrew Cooper <andrew.cooper3@citrix.com>
Furthermore, we'll expect this to fail on 4.11 and later, until we can
fix the livepatch build tools interaction with altinstructions.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-11-01 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 15:53 [OSSTEST PATCH 1/2] mfi-common: Do not set enable_livepatch on build-*-prev Ian Jackson
2018-11-01 15:53 ` [OSSTEST PATCH 2/2] mfi-common: Enable livepatch tests in 4.10 and 4.11 as intended (!) Ian Jackson
2018-11-01 15:58 ` Andrew Cooper [this message]
2018-11-01 16:04 ` 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=1aefcd8a-698e-c88f-b381-aade8aef6bef@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=konrad.wilk@oracle.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 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.