On 2/24/20 4:11 PM, Eric Blake wrote:
On 2/23/20 12:51 AM, Yoshinori Sato wrote:Tested-by: Philippe Mathieu-Daudé <phi...@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <phi...@redhat.com> Signed-off-by: Yoshinori Sato <ys...@users.sourceforge.jp> Message-Id: <20190607091116.49044-17-ys...@users.sourceforge.jp> Signed-off-by: Richard Henderson <richard.hender...@linaro.org> pick ed65c02993 target/rx: Add RX to SysEmuTarget pick 01372568ae tests: Add rx to machine-none-test.c [PMD: Squashed patches from Richard Henderson modifying qapi/common.json and tests/machine-none-test.c] Signed-off-by: Philippe Mathieu-Daudé <phi...@redhat.com> ---+++ b/qapi/machine.json @@ -26,7 +26,7 @@ 'data' : [ 'aarch64', 'alpha', 'arm', 'cris', 'hppa', 'i386', 'lm32', 'm68k', 'microblaze', 'microblazeel', 'mips', 'mips64', 'mips64el', 'mipsel', 'moxie', 'nios2', 'or1k', 'ppc', - 'ppc64', 'riscv32', 'riscv64', 's390x', 'sh4', + 'ppc64', 'riscv32', 'riscv64', 'rx', 's390x', 'sh4',Missing mention of the new enum member with a 'since 5.0' designation in the documentation.
Is this something we can automate? Maybe dumping all the qapi data when we do a release, then check the differences before the next release?