Marc-André Lureau writes:
> Hi
>
> On Tue, May 16, 2017 at 9:33 PM Markus Armbruster wrote:
>
>> On the subject: there is no such thing as "QUInt". I guess you mean
>> "uint type" (like in PATCH 06's subject). Could also say "QNUM_U64".
>>
>> Apropos subject: humor me, and start your subjects
Hi
On Tue, May 16, 2017 at 9:33 PM Markus Armbruster wrote:
> On the subject: there is no such thing as "QUInt". I guess you mean
> "uint type" (like in PATCH 06's subject). Could also say "QNUM_U64".
>
> Apropos subject: humor me, and start your subjects with a capital
> letter, like this:
>
Markus Armbruster writes:
> On the subject: there is no such thing as "QUInt". I guess you mean
> "uint type" (like in PATCH 06's subject). Could also say "QNUM_U64".
>
> Apropos subject: humor me, and start your subjects with a capital
> letter, like this:
>
> qapi: Update the qobject visi
On the subject: there is no such thing as "QUInt". I guess you mean
"uint type" (like in PATCH 06's subject). Could also say "QNUM_U64".
Apropos subject: humor me, and start your subjects with a capital
letter, like this:
qapi: Update the qobject visitor ...
Marc-André Lureau writes:
> S
Switch to use QNum/uint where appropriate to remove i64 limitation.
The input visitor will cast i64 input to u64 for compatibility
reasons (existing json QMP client already use negative i64 for large
u64, and expect an implicit cast in qemu).
Signed-off-by: Marc-André Lureau
---
qapi/qobject-in
