From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Support T/t for guest memory sizes
Date: Tue, 14 Sep 2010 16:41:54 +0200 [thread overview]
Message-ID: <4C8F89B2.3010902@redhat.com> (raw)
In-Reply-To: <4C8F800B.2090304@codemonkey.ws>
On 09/14/10 16:00, Anthony Liguori wrote:
> On 09/14/2010 08:37 AM, Jes.Sorensen@redhat.com wrote:
>> From: Jes Sorensen<Jes.Sorensen@redhat.com>
>>
>> Signed-off-by: Jes Sorensen<Jes.Sorensen@redhat.com>
>>
>
> anthony@titi:~/git/qemu$ grep "case 'G': case 'g':" *.c
> monitor.c: case 'G': case 'g':
> vl.c: case 'G': case 'g':
> vl.c: case 'G': case 'g':
>
> So there's more locations to fixup. But while you're touching this
> code, it probably makes sense to add a str_to_bytes() function to
> cutils.c to make sure we accept things consistently for the future.
Fair enough, I'll have a look.
Cheers,
Jes
prev parent reply other threads:[~2010-09-14 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 13:37 [Qemu-devel] [PATCH] Support T/t for guest memory sizes Jes.Sorensen
2010-09-14 14:00 ` [Qemu-devel] " Anthony Liguori
2010-09-14 14:41 ` Jes Sorensen [this message]
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=4C8F89B2.3010902@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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).