From: Paolo Bonzini <pbonzini@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Re: [PULL] pci, vhost fixes
Date: Mon, 31 May 2010 14:51:26 +0200 [thread overview]
Message-ID: <4C03B0CE.3040102@redhat.com> (raw)
In-Reply-To: <AANLkTinseMLzGGS9N-bc8djjEQIfcC_i-sJRereCCIiv@mail.gmail.com>
On 05/30/2010 08:19 PM, Blue Swirl wrote:
> We have PRI*64 just for this purpose, so let's use them. The
> discussion about that was earlier.
How does mingw matter for vhost-net specific code?
Paolo
next prev parent reply other threads:[~2010-05-31 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-30 15:50 [Qemu-devel] [PULL] pci, vhost fixes Michael S. Tsirkin
2010-05-30 16:56 ` Blue Swirl
2010-05-30 18:05 ` Michael S. Tsirkin
2010-05-30 18:19 ` Blue Swirl
2010-05-30 18:58 ` Michael S. Tsirkin
2010-05-30 19:15 ` Blue Swirl
2010-05-31 12:51 ` Paolo Bonzini [this message]
2010-05-31 13:35 ` [Qemu-devel] " Michael S. Tsirkin
2010-05-31 18:29 ` Blue Swirl
2010-06-01 5:32 ` Markus Armbruster
2010-06-01 17:13 ` Blue Swirl
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=4C03B0CE.3040102@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=mst@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).