From: Eric Blake <eblake@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/9] runstate: create runstate_index function
Date: Mon, 18 May 2015 08:55:04 -0600 [thread overview]
Message-ID: <5559FD48.9070405@redhat.com> (raw)
In-Reply-To: <20150518095834.GC2201@work-vm>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On 05/18/2015 03:58 AM, Dr. David Alan Gilbert wrote:
> * Juan Quintela (quintela@redhat.com) wrote:
>> Given a string state, we need a way to get the RunState for that string.
>>
>> Signed-off-by: Juan Quintela <quintela@redhat.com>
>> ---
>> include/sysemu/sysemu.h | 1 +
>> vl.c | 13 +++++++++++++
>> 2 files changed, 14 insertions(+)
>>
>>
>> +RunState runstate_index(char *str)
>> +{
>> + RunState i = 0;
>> +
>> + while (i != RUN_STATE_MAX) {
>> + if (strcmp(str, RunState_lookup[i]) == 0) {
>> + return i;
>> + }
>> + i++;
>> + }
>> + return -1;
>
> It doesn't seem right to return -1 for the value of an enum
> (which is otherwise used as an index into an array of strings).
>
> Make it return a bool and pass the RunState* as a parameter ?
Why open-code this, when we already have qapi_enum_parse() in
qapi/qapi-util.c?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-05-18 14:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 16:28 [Qemu-devel] [PATCH 0/9] Optional toplevel sections Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 1/9] migration: create savevm_state Juan Quintela
2015-05-18 9:15 ` Dr. David Alan Gilbert
2015-05-14 16:28 ` [Qemu-devel] [PATCH 2/9] migration: Use normal VMStateDescriptions for Subsections Juan Quintela
2015-05-18 9:54 ` Dr. David Alan Gilbert
2015-05-14 16:28 ` [Qemu-devel] [PATCH 3/9] runstate: Add runstate store Juan Quintela
2015-05-18 10:35 ` Dr. David Alan Gilbert
2015-06-17 0:28 ` Juan Quintela
2015-05-18 10:38 ` Denis V. Lunev
2015-05-18 14:50 ` Eric Blake
2015-06-17 0:55 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 4/9] runstate: create runstate_index function Juan Quintela
2015-05-18 9:58 ` Dr. David Alan Gilbert
2015-05-18 14:55 ` Eric Blake [this message]
2015-06-17 0:31 ` Juan Quintela
2015-06-17 0:55 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 5/9] runstate: migration allows more transitions now Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 6/9] migration: create new section to store global state Juan Quintela
2015-05-18 10:23 ` Dr. David Alan Gilbert
2015-06-17 1:10 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 7/9] global_state: Make section optional Juan Quintela
2015-05-18 11:03 ` Dr. David Alan Gilbert
2015-06-17 1:25 ` Juan Quintela
2015-05-14 16:28 ` [Qemu-devel] [PATCH 8/9] vmstate: Create optional sections Juan Quintela
2015-05-18 11:23 ` Dr. David Alan Gilbert
2015-05-19 9:17 ` Dr. David Alan Gilbert
2015-05-14 16:28 ` [Qemu-devel] [PATCH 9/9] migration: Add configuration section Juan Quintela
2015-05-18 11:39 ` Dr. David Alan Gilbert
2015-06-17 1:39 ` Juan Quintela
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=5559FD48.9070405@redhat.com \
--to=eblake@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).