From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH build fix] migration: do not doubly-define LoadStateHandler
Date: Thu, 15 Jun 2017 10:54:45 +0100 [thread overview]
Message-ID: <CAFEAcA8PkOJr0u1zF9N-Ye_zcraqc99d9109GdFcxc2FANwmfg@mail.gmail.com> (raw)
In-Reply-To: <1497520197-56796-1-git-send-email-pbonzini@redhat.com>
On 15 June 2017 at 10:49, Paolo Bonzini <pbonzini@redhat.com> wrote:
> As the simplest fix to un-confuse patchew, inline the type
> in struct VMStateDescription. As there are no users of
> LoadStateHandler anymore in e.g. function declarations,
> there isn't much advantage in defining it as a type.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
I'm currently processing Juan's pullrequest which includes
a fix for this (it moves the typedefs into typedefs.h.)
thanks
-- PMM
prev parent reply other threads:[~2017-06-15 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 9:49 [Qemu-devel] [PATCH build fix] migration: do not doubly-define LoadStateHandler Paolo Bonzini
2017-06-15 9:54 ` Peter Maydell [this message]
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=CAFEAcA8PkOJr0u1zF9N-Ye_zcraqc99d9109GdFcxc2FANwmfg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--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).