From: Anthony Liguori <anthony@codemonkey.ws>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Hans de Bruin <bruinjm@xs4all.nl>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: v0.11.0-rc0-347-g562593a - pci-hotplug.c buildfailure
Date: Sat, 15 Aug 2009 18:17:09 -0500 [thread overview]
Message-ID: <4A8741F5.7020404@codemonkey.ws> (raw)
In-Reply-To: <D5E423455F0B45639F15188EA7CD26DA@FSCPC>
Sebastian Herbszt wrote:
>
> Anthony, there is a second report [1] about this problem. The
> following patch makes
> the compiler happy.
Please post as a top level patch with a Signed-off-by.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-08-15 23:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 21:16 [Qemu-devel] v0.11.0-rc0-347-g562593a - pci-hotplug.c build failure Sebastian Herbszt
2009-08-10 21:50 ` Anthony Liguori
2009-08-10 22:00 ` Sebastian Herbszt
2009-08-15 21:21 ` [Qemu-devel] Re: v0.11.0-rc0-347-g562593a - pci-hotplug.c buildfailure Sebastian Herbszt
2009-08-15 23:17 ` Anthony Liguori [this message]
2009-08-15 21:32 ` [Qemu-devel] v0.11.0-rc0-347-g562593a - pci-hotplug.c build failure Sebastian Herbszt
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=4A8741F5.7020404@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=bruinjm@xs4all.nl \
--cc=herbszt@gmx.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).