All of lore.kernel.org
 help / color / mirror / Atom feed
* __XEN_LATEST_INTERFACE_VERSION__ is still 0x00040600 in staging
@ 2015-09-14 11:53 Razvan Cojocaru
  2015-09-14 12:13 ` Jan Beulich
  0 siblings, 1 reply; 3+ messages in thread
From: Razvan Cojocaru @ 2015-09-14 11:53 UTC (permalink / raw)
  To: xen-devel@lists.xen.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

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: __XEN_LATEST_INTERFACE_VERSION__ is still 0x00040600 in staging
  2015-09-14 11:53 __XEN_LATEST_INTERFACE_VERSION__ is still 0x00040600 in staging Razvan Cojocaru
@ 2015-09-14 12:13 ` Jan Beulich
  2015-09-14 12:19   ` Razvan Cojocaru
  0 siblings, 1 reply; 3+ messages in thread
From: Jan Beulich @ 2015-09-14 12:13 UTC (permalink / raw)
  To: Razvan Cojocaru; +Cc: xen-devel@lists.xen.org

>>> On 14.09.15 at 13:53, <rcojocaru@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

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: __XEN_LATEST_INTERFACE_VERSION__ is still 0x00040600 in staging
  2015-09-14 12:13 ` Jan Beulich
@ 2015-09-14 12:19   ` Razvan Cojocaru
  0 siblings, 0 replies; 3+ messages in thread
From: Razvan Cojocaru @ 2015-09-14 12:19 UTC (permalink / raw)
  To: Jan Beulich; +Cc: xen-devel@lists.xen.org

On 09/14/2015 03:13 PM, Jan Beulich wrote:
>>>> On 14.09.15 at 13:53, <rcojocaru@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?

None, at least as far as my code is concerned. It's just that I've
already added a new libxc helper function with assorted HV-side code and
just assumed that __XEN_LATEST_INTERFACE_VERSION__ had been bumped to
0x00040700, so some of my own code wasn't being compiled as it depended
on that value. Of course, there's nothing wrong with the current
approach, I was just curious if bumps happen as soon as a new version is
out or only when the interface changes.


Thanks,
Razvan

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-09-14 12:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-14 11:53 __XEN_LATEST_INTERFACE_VERSION__ is still 0x00040600 in staging Razvan Cojocaru
2015-09-14 12:13 ` Jan Beulich
2015-09-14 12:19   ` Razvan Cojocaru

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.