On Thu, 2016-04-14 at 18:07 +0100, Ian Jackson wrote: > Signed-off-by: Ian Jackson > CC: Jan Beulich > CC: Tim Deegan > Reviewed-by: Dario Faggioli One thing, out of curiosity. This syntax, here: > -/* XEN_SYSCTL_cpupool_op */ > +/* ` enum XEN_SYSCTL_cpupool_op { */ >  #define XEN_SYSCTL_CPUPOOL_OP_CREATE                1  /* C */ >  #define XEN_SYSCTL_CPUPOOL_OP_DESTROY               2  /* D */ >  #define XEN_SYSCTL_CPUPOOL_OP_INFO                  3  /* I */ > @@ -546,9 +546,10 @@ DEFINE_XEN_GUEST_HANDLE(xen_sysctl_numainfo_t); >  #define XEN_SYSCTL_CPUPOOL_OP_RMCPU                 5  /* R */ >  #define XEN_SYSCTL_CPUPOOL_OP_MOVEDOMAIN            6  /* M */ >  #define XEN_SYSCTL_CPUPOOL_OP_FREEINFO              7  /* F */ > +/* ` } */ >  #define XEN_SYSCTL_CPUPOOL_PAR_ANY     0xFFFFFFFF >  struct xen_sysctl_cpupool_op { > -    uint32_t op;          /* IN */ > +    uint32_t op;          /* IN ` enum XEN_SYSCTL_cpupool_op ` */ > and here, is I guess useful to the hypercall HTML docs generator, as mentioned in the cover letter? It is not something we do in many other places (if at all, at least in this file)... If it is, I'll happily add to my TODO list to convert more entries to it. Regards, Dario -- <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)