Re: [PATCH v4 4/4] qapi: expose all schema features to code

John Snow writes: > On Fri, Feb 7, 2025, 6:57 AM Markus Armbruster wrote: > >> Daniel P. Berrangé writes: >> >> > This replaces use of the constants from the QapiSpecialFeatures >> > enum, with constants from the auto-generate QapiFeatures enum >> > in qapi-features.h >> > >> > The 'deprecated'

Re: [PATCH v4 4/4] qapi: expose all schema features to code

On Fri, Feb 7, 2025, 6:57 AM Markus Armbruster wrote: > Daniel P. Berrangé writes: > > > This replaces use of the constants from the QapiSpecialFeatures > > enum, with constants from the auto-generate QapiFeatures enum > > in qapi-features.h > > > > The 'deprecated' and 'unstable' features still

Re: [PATCH v4 4/4] qapi: expose all schema features to code

Daniel P. Berrangé writes: > This replaces use of the constants from the QapiSpecialFeatures > enum, with constants from the auto-generate QapiFeatures enum > in qapi-features.h > > The 'deprecated' and 'unstable' features still have a little bit of > special handling, being force defined to be t

Re: [PATCH v4 4/4] qapi: expose all schema features to code

Daniel P. Berrangé writes: > This replaces use of the constants from the QapiSpecialFeatures > enum, with constants from the auto-generate QapiFeatures enum > in qapi-features.h > > The 'deprecated' and 'unstable' features still have a little bit of > special handling, being force defined to be t

[PATCH v4 4/4] qapi: expose all schema features to code

This replaces use of the constants from the QapiSpecialFeatures enum, with constants from the auto-generate QapiFeatures enum in qapi-features.h The 'deprecated' and 'unstable' features still have a little bit of special handling, being force defined to be the 1st + 2nd features in the enum, regar