Marc-André Lureau 67596f7485 qapi: Do not define enumeration value explicitly ... The generated C enumeration types explicitly set the enumeration constants to 0, 1, 2, ... That's exactly what you get when you don't supply values. Drop the explicit values. No change now, but it will avoid gaps in the values when we later add support for 'if' conditions. Avoiding such gaps will save us the trouble of changing the ENUM_lookup[] tables to work without a sentinel. We'll have to take care to ensure the headers required by the 'if' conditions get always included before the generated QAPI code. Fortunately, our convention to include "qemu/osdep.h" first in any .c ensures that's the case for our CONFIG_FOO macros Backports commit 9c2f56e9f9d5a1f9ddac77dda35f997738e85d11 from qemu		2018-12-18 05:03:22 -05:00
..
qapi	qapi: Do not define enumeration value explicitly	2018-12-18 05:03:22 -05:00
create_config	Revert "Makefile: Rename TARGET_DIRS to TARGET_LIST"	2018-07-05 17:40:24 -04:00
decodetree.py	decodetree: Allow multiple input files	2018-11-11 08:28:55 -05:00
make_device_config.sh	fix file perms	2015-08-28 21:05:38 -07:00
ordereddict.py	import	2015-08-21 15:04:50 +08:00
qapi-gen.py	qapi: Lift error reporting from QAPISchema.__init__() to callers	2018-03-09 08:55:45 -05:00