From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] memory: Print region priority
Date: Sun, 02 Oct 2011 16:08:10 +0200 [thread overview]
Message-ID: <4E88704A.2080907@redhat.com> (raw)
In-Reply-To: <4E81C8EF.3020900@siemens.com>
On 09/27/2011 04:00 PM, Jan Kiszka wrote:
> Useful to discover eclipses.
>
> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
> ---
>
> PS: Current memory/master requires an obvious build fix (central
> definition of some types), but I assume you already have a patch in
> your tree.
>
No, doesn't happen here.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-10-02 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 13:00 [Qemu-devel] [PATCH 1/3] memory: Print region priority Jan Kiszka
2011-10-02 14:08 ` Avi Kivity [this message]
2011-10-02 16:42 ` [Qemu-devel] [PATCH] memory: Push typedefs into qemu-common Jan Kiszka
2011-10-02 17:00 ` Avi Kivity
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=4E88704A.2080907@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.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).