qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH 0/3] Extract non-QDicts in qdict_array_split()
Date: Fri, 21 Feb 2014 19:11:38 +0100	[thread overview]
Message-ID: <1393006301-22514-1-git-send-email-mreitz@redhat.com> (raw)

Currently, qdict_array_split() splits a QDict like
  { "0.a": 42, "1": 23, "2.b": 84 }
into the QList
  [ { "a": 42 } ]
with the QDict still being
  { "1": 23, "2.b": 84 }

However, it makes more sense to create the QList
  [ { "a": 42 }, 23, { "b": 84 } ]
and having emptied the QDict.

This is implemented by this series.


Max Reitz (3):
  qemu-config: Sections must consist of keys
  qdict: Extract non-QDicts in qdict_array_split()
  check-qdict: Adjust test for qdict_array_split()

 qobject/qdict.c     | 60 ++++++++++++++++++++++++++++++++++++++++-------------
 tests/check-qdict.c | 22 ++++++++++++++------
 util/qemu-config.c  |  6 ++++++
 3 files changed, 68 insertions(+), 20 deletions(-)

-- 
1.9.0

             reply	other threads:[~2014-02-21 18:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 18:11 Max Reitz [this message]
2014-02-21 18:11 ` [Qemu-devel] [PATCH 1/3] qemu-config: Sections must consist of keys Max Reitz
2014-02-21 18:22   ` Eric Blake
2014-02-21 18:11 ` [Qemu-devel] [PATCH 2/3] qdict: Extract non-QDicts in qdict_array_split() Max Reitz
2014-02-21 18:37   ` Eric Blake
2014-02-21 19:40     ` Max Reitz
2014-02-21 18:11 ` [Qemu-devel] [PATCH 3/3] check-qdict: Adjust test for qdict_array_split() Max Reitz
2014-02-21 18:39   ` Eric Blake
2014-02-21 19:41     ` Max Reitz
2014-02-21 21:17 ` [Qemu-devel] [PATCH 0/3] Extract non-QDicts in qdict_array_split() Kevin Wolf
2014-02-21 22:32 ` Eric Blake
2014-02-26 17:16   ` Max Reitz
2014-02-26 18:18     ` Eric Blake

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=1393006301-22514-1-git-send-email-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).