From: "Radim Krčmář" <rkrcmar@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Michael Walle <michael@walle.cc>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-trivial] [PATCH 0/2] Fix GCC 5.0.0 build errors
Date: Fri, 20 Feb 2015 18:04:44 +0100 [thread overview]
Message-ID: <20150220170443.GD3974@potion.brq.redhat.com> (raw)
In-Reply-To: <1424448376-15599-1-git-send-email-rkrcmar@redhat.com>
Cc: qemu-trivial@nongnu.org
WARNING: multiple messages have this Message-ID (diff)
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Michael Walle <michael@walle.cc>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] Fix GCC 5.0.0 build errors
Date: Fri, 20 Feb 2015 18:04:44 +0100 [thread overview]
Message-ID: <20150220170443.GD3974@potion.brq.redhat.com> (raw)
In-Reply-To: <1424448376-15599-1-git-send-email-rkrcmar@redhat.com>
Cc: qemu-trivial@nongnu.org
next prev parent reply other threads:[~2015-02-20 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 16:06 [Qemu-devel] [PATCH 0/2] Fix GCC 5.0.0 build errors Radim Krčmář
2015-02-20 16:06 ` [Qemu-devel] [PATCH 1/2] fix GCC 5.0.0 logical-not-parentheses warnings Radim Krčmář
2015-03-04 14:36 ` Michael Tokarev
2015-03-04 16:27 ` Radim Krčmář
2015-02-20 16:06 ` [Qemu-devel] [PATCH 2/2] milkymist-pfpu: fix GCC 5.0.0 aggressive-loop-optimizations warning Radim Krčmář
2015-02-23 17:32 ` [Qemu-trivial] " Michael Walle
2015-02-23 17:32 ` [Qemu-devel] " Michael Walle
2015-02-20 17:04 ` Radim Krčmář [this message]
2015-02-20 17:04 ` [Qemu-devel] [PATCH 0/2] Fix GCC 5.0.0 build errors Radim Krčmář
2015-03-04 14:38 ` [Qemu-trivial] " Michael Tokarev
2015-03-04 14:38 ` [Qemu-devel] " 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=20150220170443.GD3974@potion.brq.redhat.com \
--to=rkrcmar@redhat.com \
--cc=michael@walle.cc \
--cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.