From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v4 0/8] spapr: bootindex support
Date: Wed, 11 Dec 2013 11:36:10 +0100 [thread overview]
Message-ID: <52A8401A.3020904@redhat.com> (raw)
In-Reply-To: <1386757341-12154-1-git-send-email-aik@ozlabs.ru>
Il 11/12/2013 11:22, Alexey Kardashevskiy ha scritto:
> With the great help from Paolo, I am presenting yet another try of bootindex
> support on sPAPR, this time with some QOM fixes. Details are in the commit messages.
> Please, comment. Thanks.
>
> Alexey Kardashevskiy (5):
> boot: extend get_boot_devices_list() to ignore suffixes
> spapr-llan: add to boot device list
> spapr-vio: fix firmware names
> qdev: introduce FWPathProvider interface
> spapr: define interface to fix device pathname
>
> Hervé Poussineau (1):
> qom: detect bad reentrance during object_class_foreach
>
> Paolo Bonzini (2):
> qom: do not register interface "types" in the type table
> vl: allow customizing the class of /machine
>
> hw/core/Makefile.objs | 1 +
> hw/core/fw-path-provider.c | 34 ++++++++++++++++++
> hw/core/qdev.c | 18 +++++++++-
> hw/net/spapr_llan.c | 3 ++
> hw/nvram/fw_cfg.c | 2 +-
> hw/ppc/spapr.c | 80 ++++++++++++++++++++++++++++++++++++++++++-
> hw/ppc/spapr_vio.c | 2 ++
> include/hw/boards.h | 1 +
> include/hw/fw-path-provider.h | 31 +++++++++++++++++
> include/sysemu/sysemu.h | 2 +-
> qom/object.c | 17 +++++++--
> tests/Makefile | 1 +
> vl.c | 11 ++++--
> 13 files changed, 193 insertions(+), 10 deletions(-)
> create mode 100644 hw/core/fw-path-provider.c
> create mode 100644 include/hw/fw-path-provider.h
>
Acked-by: Paolo Bonzini <pbonzini@redhat.com>
next prev parent reply other threads:[~2013-12-11 10:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 10:22 [Qemu-devel] [PATCH v4 0/8] spapr: bootindex support Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 1/8] qom: do not register interface "types" in the type table Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 2/8] qom: detect bad reentrance during object_class_foreach Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 3/8] boot: extend get_boot_devices_list() to ignore suffixes Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 4/8] spapr-llan: add to boot device list Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 5/8] spapr-vio: fix firmware names Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 6/8] qdev: introduce FWPathProvider interface Alexey Kardashevskiy
2014-02-20 12:01 ` Andreas Färber
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 7/8] vl: allow customizing the class of /machine Alexey Kardashevskiy
2013-12-11 10:22 ` [Qemu-devel] [PATCH v4 8/8] spapr: define interface to fix device pathname Alexey Kardashevskiy
2013-12-11 10:36 ` Paolo Bonzini [this message]
2013-12-12 14:05 ` [Qemu-devel] [PATCH v4 0/8] spapr: bootindex support Michael S. Tsirkin
2013-12-13 3:19 ` Alexey Kardashevskiy
2014-01-22 4:19 ` Alexey Kardashevskiy
2014-01-22 10:16 ` Paolo Bonzini
2014-01-22 12:17 ` Alexey Kardashevskiy
2014-02-14 3:25 ` Alexey Kardashevskiy
2014-02-14 7:29 ` Paolo Bonzini
2014-02-14 8:26 ` Alexey Kardashevskiy
2014-02-20 8:37 ` Alexey Kardashevskiy
2014-02-20 11:09 ` Paolo Bonzini
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=52A8401A.3020904@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).