From: Igor Mammedov <imammedo@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: anthony@codemonkey.ws, jan.kiszka@web.de, qemu-devel@nongnu.org,
gleb@redhat.com, ehabkost@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC qom-cpu-next] apic: QOM'ify APICCommonState casts
Date: Mon, 29 Apr 2013 12:29:48 +0200 [thread overview]
Message-ID: <20130429122948.41f3e03e@thinkpad> (raw)
In-Reply-To: <1367148131-1440-1-git-send-email-afaerber@suse.de>
On Sun, 28 Apr 2013 13:22:10 +0200
Andreas Färber <afaerber@suse.de> wrote:
> Necessary to change the name of ICCDevice's parent object field.
>
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> Could any of the APIC experts please review whether I'm touching any hot path?
> Not sure if this was a mix of pre- and post-QOM code or intentional... Thanks.
>
> hw/i386/kvm/apic.c | 4 ++--
> hw/intc/apic.c | 20 +++++++++++---------
> hw/intc/apic_common.c | 10 +++++-----
> include/hw/cpu/icc_bus.h | 2 +-
> 4 files changed, 19 insertions(+), 17 deletions(-)
>
[...]
>
> diff --git a/include/hw/cpu/icc_bus.h b/include/hw/cpu/icc_bus.h
> index b550070..f2c8a50 100644
> --- a/include/hw/cpu/icc_bus.h
> +++ b/include/hw/cpu/icc_bus.h
> @@ -51,7 +51,7 @@ typedef struct ICCBus {
> */
> typedef struct ICCDevice {
> /*< private >*/
> - DeviceState qdev;
> + DeviceState parent_obj;
This hunk doesn't apply to qpm-cpu-next.
It looks like it's accidentally crept in
https://github.com/afaerber/qemu-cpu/commit/a7ae7cd073cc2b20de3372edc84ec5a01e88e55d
> /*< public >*/
> } ICCDevice;
>
> --
> 1.8.1.4
>
>
--
Regards,
Igor
next prev parent reply other threads:[~2013-04-29 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 11:22 [Qemu-devel] [PATCH RFC qom-cpu-next] apic: QOM'ify APICCommonState casts Andreas Färber
2013-04-28 13:03 ` Jan Kiszka
2013-04-28 13:53 ` Andreas Färber
2013-04-28 14:13 ` Jan Kiszka
2013-04-29 10:29 ` Igor Mammedov [this message]
2013-04-29 11:30 ` Andreas Färber
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=20130429122948.41f3e03e@thinkpad \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--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).