From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>, None <afaerber@suse.de>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH v7 0/2] qdev: Detect duplicate device properties
Date: Tue, 26 Mar 2013 18:33:27 -0000 [thread overview]
Message-ID: <201303261833.r2QIXSLg025820@d23av03.au.ibm.com> (raw)
In-Reply-To: <1364217314-7400-1-git-send-email-peter.maydell@linaro.org>
Applied. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2013-03-26 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 13:15 [Qemu-devel] [PATCH v7 0/2] qdev: Detect duplicate device properties Peter Maydell
2013-03-25 13:15 ` [Qemu-devel] [PATCH v7 1/2] qom: Detect attempts to add a property that already exists Peter Maydell
2013-03-25 13:15 ` [Qemu-devel] [PATCH v7 2/2] hw/qdev: Abort rather than ignoring errors adding device properties Peter Maydell
2013-03-26 18:33 ` Anthony Liguori [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=201303261833.r2QIXSLg025820@d23av03.au.ibm.com \
--to=aliguori@us.ibm.com \
--cc=afaerber@suse.de \
--cc=patches@linaro.org \
--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).