From mboxrd@z Thu Jan  1 00:00:00 1970
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: __XEN_LATEST_INTERFACE_VERSION__ is still 0x00040600 in
	staging
Date: Mon, 14 Sep 2015 14:53:33 +0300
Message-ID: <55F6B53D.6050803@bitdefender.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Hello,

I've found this out by accident, since I have some code that does some
#ifdef tricks based on __XEN_LATEST_INTERFACE_VERSION__, but while
running staging ("Xen version 4.7-unstable") it seems that in
xen/xen-compat.h we still have:

#define __XEN_LATEST_INTERFACE_VERSION__ 0x00040600

Is this intended?


Thanks,
Razvan