On Wed, Jan 14, 2015 at 11:43:31AM +0000, Jan Beulich wrote:
> >>> On 14.01.15 at 12:31, <ian.campb...@citrix.com> wrote:
> > On Wed, 2015-01-14 at 10:36 +0000, Jan Beulich wrote:
> >> while we don't have any changes in the public interface depending on
> >> __XEN_INTERFACE_VERSION__ <relation> 0x00040500, shouldn't
> >> we nevertheless update xen-compat.h's
> >> __XEN_LATEST_INTERFACE_VERSION__ for 4.5?
> > 
> > We probably should have done, but I think it is too late now unless we
> > think we could justify force pushing such a change, which I doubt.
> > 
> > I think it's a bit of a tree falling in the woods change anyway, if
> > there are no relevant changes would anyone notice if it remained at 4.4?
> 
> I noticed when I wanted to set the XEN_INTERFACE_VERSION config
> option to 0x00040500 in the 2.6.18-xen tree.
> 
> > Perhaps for 4.5.1? (But it doesn't sound entirely stable release
> > material too me...)
> 
> If we were to do such a change on master only, I think I'd backport
> it for 4.5.1 irrespective of how important we'd consider such a change.

<nods> I concur. 
> 
> Jan
> 

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

Reply via email to