[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] physdev: hide compatibility definitions for new enough interface version

To: Jan Beulich <JBeulich@xxxxxxxx>
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Mon, 19 Jan 2015 10:36:21 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>
Delivery-date: Mon, 19 Jan 2015 10:36:45 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On Thu, 2015-01-15 at 15:27 +0000, Jan Beulich wrote:
> There's no point in continuing to expose those.

There's a chance someone might have been using them for
__XEN_INTERFACE_VERSION__ >= 0x00030202, I think.

Given that we missed the opportunity to gate these when the change was
made we should probably use the current/next version to actually remove
them, with a comment to explain.

Unless we are certain noone in the wild is actually using them.

Ian.


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

Follow-Ups:
- Re: [Xen-devel] [PATCH] physdev: hide compatibility definitions for new enough interface version
  - From: Jan Beulich

References:
- [Xen-devel] [PATCH] physdev: hide compatibility definitions for new enough interface version
  - From: Jan Beulich

Prev by Date: Re: [Xen-devel] [PATCH 3/6] xen/arm: kernel: Move kernel loading code in init section
Next by Date: Re: [Xen-devel] [RFC] Add the panic info when disable VT-d
Previous by thread: [Xen-devel] [PATCH] physdev: hide compatibility definitions for new enough interface version
Next by thread: Re: [Xen-devel] [PATCH] physdev: hide compatibility definitions for new enough interface version
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.