Re: [Qemu-block] [PATCH v12 22/36] qapi: Don't let implicit enum MAX member collide

Eric Blake wrote: > Now that we guarantee the user doesn't have any enum values > beginning with a single underscore, we can use that for our > own purposes. Renaming ENUM_MAX to ENUM__MAX makes it obvious > that the sentinel is generated. > > This patch was mostly generated

[Qemu-block] [PATCH v12 22/36] qapi: Don't let implicit enum MAX member collide

Now that we guarantee the user doesn't have any enum values beginning with a single underscore, we can use that for our own purposes. Renaming ENUM_MAX to ENUM__MAX makes it obvious that the sentinel is generated. This patch was mostly generated by applying a temporary patch: |diff --git