From: Olaf Hering <olaf@aepfle.de>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [ANNOUNCE] First release candidates for Xen 4.0.4 and 4.1.3
Date: Wed, 9 May 2012 22:30:57 +0200 [thread overview]
Message-ID: <20120509203057.GA19370@aepfle.de> (raw)
In-Reply-To: <4FAAC12F.8010507@citrix.com>
On Wed, May 09, Andrew Cooper wrote:
> If it is failing -Warray-bounds then the source code probably needs fixing.
>
> Do you have a log of the failures caused by -Warray-bounds ?
http://lists.xen.org/archives/html/xen-devel/2012-03/msg02583.html
Olaf
next prev parent reply other threads:[~2012-05-09 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 12:58 [ANNOUNCE] First release candidates for Xen 4.0.4 and 4.1.3 Keir Fraser
2012-05-07 17:18 ` Pavel Matěja
2012-05-07 20:03 ` Keir Fraser
2012-05-07 20:08 ` Andrew Cooper
2012-05-07 20:52 ` M A Young
2012-05-08 7:50 ` Keir Fraser
2012-05-09 19:03 ` M A Young
2012-05-09 19:10 ` Andrew Cooper
2012-05-09 20:30 ` Olaf Hering [this message]
2012-05-11 15:51 ` Olaf Hering
2012-05-14 10:09 ` Jan Beulich
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=20120509203057.GA19370@aepfle.de \
--to=olaf@aepfle.de \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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).