From: Wei Liu <wei.liu2@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] domctl: revert double increment of domctl version
Date: Wed, 21 Feb 2018 17:38:03 +0000 [thread overview]
Message-ID: <20180221173802.4asubsivkejs2ihy@citrix.com> (raw)
In-Reply-To: <20180221173422.10550-1-olaf@aepfle.de>
On Wed, Feb 21, 2018 at 06:34:22PM +0100, Olaf Hering wrote:
> Xen 4.10 has XEN_DOMCTL_INTERFACE_VERSION 0xe, staging should be fine
> with 0xf until the next release is prepared.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> ---
> xen/include/public/domctl.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/include/public/domctl.h b/xen/include/public/domctl.h
> index ec7a860afc..501c44230b 100644
> --- a/xen/include/public/domctl.h
> +++ b/xen/include/public/domctl.h
> @@ -38,7 +38,7 @@
> #include "hvm/save.h"
> #include "memory.h"
>
> -#define XEN_DOMCTL_INTERFACE_VERSION 0x00000010
> +#define XEN_DOMCTL_INTERFACE_VERSION 0x0000000f
>
The reason we bumped the number twice is because we want a dedicated
number to denote the recent security fix.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-21 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 17:34 [PATCH] domctl: revert double increment of domctl version Olaf Hering
2018-02-21 17:38 ` Wei Liu [this message]
2018-02-21 17:46 ` Olaf Hering
2018-02-21 17:53 ` Andrew Cooper
2018-02-21 18:14 ` Olaf Hering
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=20180221173802.4asubsivkejs2ihy@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=olaf@aepfle.de \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--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.