From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Mian M. Hamayun" <m.hamayun@virtualopensystems.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PULL v2 00/56] QOM devices patch queue 2013-10-31
Date: Sun, 3 Nov 2013 05:58:13 -0800 [thread overview]
Message-ID: <CA+aC4kt9OrsOJd3qaNqMHx-N6x9dT8PqdMBOeBbk+VmA7T7_7Q@mail.gmail.com> (raw)
In-Reply-To: <52764F63.5090501@suse.de>
On Sun, Nov 3, 2013 at 5:28 AM, Andreas Färber <afaerber@suse.de> wrote:
> Anthony,
>
>> The errors are the exact same as before. Install some VMs and
>> reproduce the problem. I just checked and it fails under 64-bit
>> Fedora 19.
>
> I have successfully booted up openSUSE 12.3 x86_64 and SLES 11 SP3
> x86_64 without any issue. You really need to explain "the problem"!
Andreas,
I told you how to reproduce the problem. If you choose not to
investigate, fine, but don't spam me with resends of a pull request
with a known breakage.
Regards,
Anthony Liguori
> Regards,
> Andreas
>
>>
>> Regards,
>>
>> Anthony Liguori
>>
>>> v2 is rebased, dropping two ARM patches, and the observed SD segfault had been
>>> fixed in 794cbc26eb94ce13c75d105eea9ff0afff56e2c2.
>>> Patches are not manually changed, thus intentionally not resent.
>>>
>>> Thanks,
>>> Andreas
>.
> --
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-11-03 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 14:37 [Qemu-devel] [PULL v2 00/56] QOM devices patch queue 2013-10-31 Andreas Färber
2013-10-31 21:03 ` Anthony Liguori
2013-11-03 13:28 ` Andreas Färber
2013-11-03 13:58 ` Anthony Liguori [this message]
2013-11-03 15:12 ` Andreas Färber
2013-11-03 16:32 ` Anthony Liguori
2013-11-03 18:47 ` Peter Maydell
2013-11-03 18:52 ` Andreas Färber
2013-11-03 18:58 ` Peter Maydell
2013-11-03 21:36 ` Andreas Färber
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=CA+aC4kt9OrsOJd3qaNqMHx-N6x9dT8PqdMBOeBbk+VmA7T7_7Q@mail.gmail.com \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=m.hamayun@virtualopensystems.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).