From: Stefan Hajnoczi <stefanha@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-trivial@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Ping http://patchwork.ozlabs.org/patch/251410/
Date: Thu, 12 Sep 2013 10:51:55 +0200 [thread overview]
Message-ID: <20130912085155.GH1965@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <5230F7D1.9090009@twiddle.net>
On Wed, Sep 11, 2013 at 04:08:01PM -0700, Richard Henderson wrote:
> There have been two patches posted for this uninitialized warning, outstanding
> since June 14. I still encounter this daily...
I'm still happy with the patch.
Michael: Do you want to take this through the trivial patches tree?
Stefan
next prev parent reply other threads:[~2013-09-12 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 23:08 [Qemu-devel] Ping http://patchwork.ozlabs.org/patch/251410/ Richard Henderson
2013-09-12 8:49 ` Peter Maydell
2013-09-12 8:51 ` Stefan Hajnoczi [this message]
2013-09-14 9:08 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=20130912085155.GH1965@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
/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).