From: Anthony Liguori <anthony@codemonkey.ws>
To: Roy Tam <roytam@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [PATCH] JSON: add %I64d support (Was: Re: [Qemu-devel] system_reset command cause assert failed)
Date: Mon, 08 Feb 2010 10:21:54 -0600 [thread overview]
Message-ID: <4B703A22.3030800@codemonkey.ws> (raw)
In-Reply-To: <473191351002040859u3d99113dy9143dcdcff0b8566@mail.gmail.com>
On 02/04/2010 10:59 AM, Roy Tam wrote:
> 2010/2/4 Luiz Capitulino<lcapitulino@redhat.com>:
>
>> On Thu, 4 Feb 2010 10:30:30 +0800
>> Roy Tam<roytam@gmail.com> wrote:
>>
>>
>>> 2010/2/4 Roy Tam<roytam@gmail.com>:
>>>
>>>> 2010/2/3 Luiz Capitulino<lcapitulino@redhat.com>:
>>>>
>>> OK we are fooled by the json lexer and parser. As we use %I64d to
>>> print 'long long' variables in Win32, but lexer and parser only deal
>>> with %lld but not %I64d, this patch add support for %I64d and solve
>>> 'info pci', 'powser_reset' and 'power_powerdown' assert failure in
>>> Win32.
>>>
>> Hm, I guess this has been suggested before... Anthony?
>>
>>
> OK I just missed this. And the wheel was reinvented. :-S
> http://www.mail-archive.com/qemu-devel@nongnu.org/msg23983.html
>
I asked for the json parser changes to be split from the PRId64
changes. It was never resubmitted. I'll apply your patch.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-02-08 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 2:30 [PATCH] JSON: add %I64d support (Was: Re: [Qemu-devel] system_reset command cause assert failed) Roy Tam
2010-02-04 2:34 ` Roy Tam
2010-02-04 14:24 ` Luiz Capitulino
2010-02-04 16:59 ` Roy Tam
2010-02-08 16:21 ` Anthony Liguori [this message]
2010-02-10 19:28 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B703A22.3030800@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roytam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).