qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"David Gibson" <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PULL v2 0/4] QOM devices patch queue 2016-01-18
Date: Mon, 18 Jan 2016 18:36:21 +0100	[thread overview]
Message-ID: <1453138585-22738-1-git-send-email-afaerber@suse.de> (raw)

Hello Peter,

This is my QOM (devices) patch queue. Please pull.

v2 fixes an annoying git-send-email RFC822 breakage by reverting a MAINTAINERS change.
I had reported it and already re-sent a previous pull; still not fixed, so fixing it myself.

Regards,
Andreas

Cc: Peter Maydell <peter.maydell@linaro.org>
Cc: Daniel P. Berrange <berrange@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>

The following changes since commit 46188349ad7e23abef0e453d2b0406985f6552a1:

  Merge remote-tracking branch 'remotes/kraxel/tags/pull-ui-20160118-1' into staging (2016-01-18 16:00:47 +0000)

are available in the git repository at:

  git://github.com/afaerber/qemu-cpu.git tags/qom-devices-for-peter

for you to fetch changes up to 300b115ce804cb6a20acc0003cc17687545b728d:

  MAINTAINERS: Fix sPAPR entry heading (2016-01-18 18:19:35 +0100)

----------------------------------------------------------------
QOM infrastructure fixes and device conversions

* Dynamic class properties
* Property iterator cleanup
* Device hot-unplug ID race fix

----------------------------------------------------------------
Andreas Färber (1):
      MAINTAINERS: Fix sPAPR entry heading

Daniel P. Berrange (2):
      qom: Allow properties to be registered against classes
      qom: Change object property iterator API contract

Paolo Bonzini (1):
      qdev: Free QemuOpts when the QOM path goes away

 MAINTAINERS                |   2 +-
 hw/core/qdev.c             |   4 +-
 hw/ppc/spapr_drc.c         |   7 +-
 include/qom/object.h       |  76 +++++++++++---
 net/filter.c               |   7 +-
 qmp.c                      |  14 ++-
 qom/object.c               | 252 +++++++++++++++++++++++++++++++++++++++------
 tests/check-qom-proplist.c |  38 ++++---
 vl.c                       |   7 +-
 9 files changed, 324 insertions(+), 83 deletions(-)

             reply	other threads:[~2016-01-18 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 17:36 Andreas Färber [this message]
2016-01-18 17:36 ` [Qemu-devel] [PULL v2 1/4] qom: Allow properties to be registered against classes Andreas Färber
2016-01-18 17:36 ` [Qemu-devel] [PULL v2 2/4] qom: Change object property iterator API contract Andreas Färber
2016-01-18 17:36 ` [Qemu-devel] [PULL v2 3/4] qdev: Free QemuOpts when the QOM path goes away Andreas Färber
2016-01-18 17:36 ` [Qemu-devel] [PULL v2 4/4] MAINTAINERS: Fix sPAPR entry heading Andreas Färber
2016-01-18 18:28 ` [Qemu-devel] [PULL v2 0/4] QOM devices patch queue 2016-01-18 Peter Maydell

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=1453138585-22738-1-git-send-email-afaerber@suse.de \
    --to=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).