| commit | 16110c8b366c66e4ac4c85783385b4b346e331e7 | |
| author | Markus Armbruster <armbru@redhat.com> | |
| Fri, 4 Nov 2022 16:06:54 +0000 (4 17:06 +0100) | ||
| committer | Markus Armbruster <armbru@redhat.com> | |
| Wed, 14 Dec 2022 19:04:47 +0000 (14 20:04 +0100) | ||
| tree | 60d7320312f3456a03f964def65217effa81ed1e | treesnapshot (tar.gz zip) |
| parent | 8de69efab1009d374c7f01d2536797ea009ee796 | commitdiff |
qapi crypto: Elide redundant has_FOO in generated C
The has_FOO for pointer-valued FOO are redundant, except for arrays.
They are also a nuisance to work with. Recent commit "qapi: Start to
elide redundant has_FOO in generated C" provided the means to elide
them step by step. This is the step for qapi/crypto.json.
Said commit explains the transformation in more detail. The invariant
violations mentioned there do not occur here.
Cc: Daniel P. Berrangé" <berrange@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-Id: <20221104160712.3005652-13-armbru@redhat.com>
The has_FOO for pointer-valued FOO are redundant, except for arrays.
They are also a nuisance to work with. Recent commit "qapi: Start to
elide redundant has_FOO in generated C" provided the means to elide
them step by step. This is the step for qapi/crypto.json.
Said commit explains the transformation in more detail. The invariant
violations mentioned there do not occur here.
Cc: Daniel P. Berrangé" <berrange@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-Id: <20221104160712.3005652-13-armbru@redhat.com>
| crypto/block-luks.c | diffblobblamehistory | |
| scripts/qapi/schema.py | diffblobblamehistory | |
| tests/unit/test-crypto-block.c | diffblobblamehistory |