Searched hist:f740048323398ebde9575a5730bf6d9f2a237f08 (Results 1 – 2 of 2) sorted by relevance
| /qemu/tests/unit/ |
| H A D | test-keyval.c | f740048323398ebde9575a5730bf6d9f2a237f08 Tue Feb 28 21:27:05 UTC 2017 Markus Armbruster <armbru@redhat.com> keyval: Restrict key components to valid QAPI names
Until now, key components are separated by '.'. This leaves little
room for evolving the syntax, and is incompatible with the __RFQDN_
prefix convention for downstream extensions.
Since key components will be commonly used as QAPI member names by the
QObject input visitor, we can just as well borrow the QAPI naming
rules here: letters, digits, hyphen and period starting with a letter,
with an optional __RFQDN_ prefix for downstream extensions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <1488317230-26248-20-git-send-email-armbru@redhat.com>
|
| /qemu/util/ |
| H A D | keyval.c | f740048323398ebde9575a5730bf6d9f2a237f08 Tue Feb 28 21:27:05 UTC 2017 Markus Armbruster <armbru@redhat.com> keyval: Restrict key components to valid QAPI names
Until now, key components are separated by '.'. This leaves little
room for evolving the syntax, and is incompatible with the __RFQDN_
prefix convention for downstream extensions.
Since key components will be commonly used as QAPI member names by the
QObject input visitor, we can just as well borrow the QAPI naming
rules here: letters, digits, hyphen and period starting with a letter,
with an optional __RFQDN_ prefix for downstream extensions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <1488317230-26248-20-git-send-email-armbru@redhat.com>
|