From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ioport: qemu-system-sparc64 currently broken
Date: Sat, 27 Jul 2013 10:55:57 +0200 [thread overview]
Message-ID: <51F38B1D.5050600@redhat.com> (raw)
In-Reply-To: <51F2F662.9000907@ilande.co.uk>
Il 27/07/2013 00:21, Mark Cave-Ayland ha scritto:
> I suspect that there may be multiple breakages here (as HEAD blows up
> differently with a trap failure), but this is definitely the start of
> the chain.
Yes, the fixes so far are the following:
commit 2b8fbcd87007a170a9778ec6645c06f543977067
commit 5519ad0c245860526e8d269e1cd20fe239447736
commit e11ef3d184c88a316f48ba2472dcb2937d9fa24b
commit 547e9201c52629eef71b0eb8cb48dacc50bcf759
commit e7342aa39b3193473ded24cbf2233930665796e9
but something else remains.
I'll try to debug it during the hard freeze period.
Paolo
next prev parent reply other threads:[~2013-07-27 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 22:21 [Qemu-devel] ioport: qemu-system-sparc64 currently broken Mark Cave-Ayland
2013-07-27 8:55 ` Paolo Bonzini [this message]
2013-07-27 13:33 ` Mark Cave-Ayland
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=51F38B1D.5050600@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).