>>> On 14.09.15 at 13:53, <rcojoc...@bitdefender.com> wrote:
> 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?
Was there any incompatible interface change already that would
have required bumping the value?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
