From: Gerd Hoffmann <kraxel@redhat.com>
To: Ian Molton <ian.molton@collabora.co.uk>
Cc: Paul Brook <paul@codesourcery.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OPT_SIZE parsing
Date: Tue, 17 Nov 2009 20:19:09 +0100 [thread overview]
Message-ID: <4B02F72D.2010305@redhat.com> (raw)
In-Reply-To: <4B02E746.2050007@collabora.co.uk>
On 11/17/09 19:11, Ian Molton wrote:
> Gerd Hoffmann wrote:
>> Maybe also create a common function for parsing called by both
>> parse_size() and parse_option_size() to make sure OPT_SIZE and the new
>> size property accept the same syntax?
>
> The thought crossed my mind, but then I thought that as none of the
> other parsers share common code (yet), it didn't make sense.
Well, when the parser is basically a simple strtoull() call it doesn't
make sense. For the size and the postfix processing it makes sense
IMHO, they easily get out of sync otherwise. For a 'bool' property (if
qdev gets one some day) it would make sense too I think.
> I can cook up another patch that allows the option parser to hook into
> the property parsing functions, or vice-versa, if you like?
Given that qemu-option.c is also used by the tools (qemu-img, ...) it
will be much easier to have qdev use a option parser function than the
other way around.
>> Otherwise it looks fine to me.
>
> Cool - whats the submission procedure? I can make a git branch publicly
> available or I can send patches to someone...
Just send it to the list, one of the maintainers with commit access
(most likely anthony) should pick it up. If it doesn't work try
resending after 2-3 weeks.
cheers,
Gerd
prev parent reply other threads:[~2009-11-17 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 12:37 [Qemu-devel] OPT_SIZE parsing Ian Molton
2009-11-17 13:24 ` Paul Brook
2009-11-17 14:23 ` Ian Molton
2009-11-17 16:51 ` Gerd Hoffmann
2009-11-17 18:11 ` Ian Molton
2009-11-17 19:19 ` Gerd Hoffmann [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=4B02F72D.2010305@redhat.com \
--to=kraxel@redhat.com \
--cc=ian.molton@collabora.co.uk \
--cc=paul@codesourcery.com \
--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).