From: Stefan Hajnoczi <stefanha@gmail.com>
To: Christophe Fergeau <cfergeau@redhat.com>
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH-v3 2/2] kvm: Fix unused-but-set-variable warning
Date: Fri, 10 Jun 2011 13:17:38 +0100 [thread overview]
Message-ID: <BANLkTimekZreaf7wJGr7+wCi6pKOizOKiw@mail.gmail.com> (raw)
In-Reply-To: <20110610104329.GC31768@teriyaki.cdg.redhat.com>
On Fri, Jun 10, 2011 at 11:43 AM, Christophe Fergeau
<cfergeau@redhat.com> wrote:
> Ping?
Let me add these patches to the trivial-patches tree since they
haven't been picked up.
Stefan
next prev parent reply other threads:[~2011-06-10 12:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 11:03 [Qemu-devel] [PATCH] Fix a number of unused-but-set-variable warnings (new with gcc-4.6) Hans de Goede
2011-05-17 11:25 ` Christophe Fergeau
2011-05-17 17:51 ` Aurelien Jarno
2011-05-27 10:34 ` Amit Shah
2011-05-30 10:28 ` [Qemu-devel] [PATCH 0/2] Fix unused-but-set-variable warnings Christophe Fergeau
2011-05-30 10:28 ` [Qemu-devel] [PATCH 1/2] tcg: Fix unused-but-set-variable warning Christophe Fergeau
2011-05-30 10:28 ` [Qemu-devel] [PATCH 2/2] kvm: " Christophe Fergeau
2011-05-30 10:53 ` [Qemu-devel] [PATCH 0/2] Fix unused-but-set-variable warnings Amit Shah
2011-05-30 13:56 ` Christophe Fergeau
2011-05-31 5:43 ` Amit Shah
2011-05-31 7:53 ` [Qemu-devel] [PATCH-v3 " Christophe Fergeau
2011-05-31 7:53 ` [Qemu-devel] [PATCH-v3 1/2] tcg: Fix unused-but-set-variable warning Christophe Fergeau
2011-06-03 16:35 ` Aurelien Jarno
2011-05-31 7:53 ` [Qemu-devel] [PATCH-v3 2/2] kvm: " Christophe Fergeau
2011-06-10 10:43 ` Christophe Fergeau
2011-06-10 12:17 ` Stefan Hajnoczi [this message]
2011-06-10 18:46 ` Stefan Hajnoczi
2011-06-11 7:46 ` Jan Kiszka
2011-06-11 13:06 ` Stefan Hajnoczi
2011-06-14 19:50 ` Christophe Fergeau
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=BANLkTimekZreaf7wJGr7+wCi6pKOizOKiw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=cfergeau@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).