From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Just to add one single point
Date: Sun, 08 Apr 2007 18:03:05 +0200 [thread overview]
Message-ID: <1176048185.1516.180.camel@rapid> (raw)
In-Reply-To: <20070408141101.GL21953@networkno.de>
On Sun, 2007-04-08 at 15:11 +0100, Thiemo Seufer wrote:
> J. Mayer wrote:
> [snip]
> > Mr Paul Brook did break the PREP and heathrow machines while doing
> > changes in the PCI code. There were some posts on this list reporting
> > this and he never even tried to fix what he broke. And now he's
> > complaining "I cannot test as it does not work". Looks like a bad joke,
> > no ?
>
> Actually, I believe it was a commit of mine (patch IIRC by Aurelien
> Jarno) which broke PREP. See
> http://lists.nongnu.org/archive/html/qemu-devel/2007-01/msg00166.html
Then, sorry for asserting this. Someone reported me that the patche that
breaks PREP was this one:
<http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/hw/prep_pci.c?sortby=date&r2=1.3&r1=1.2>
I have to admit I dit took the time to check, so...
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-04-08 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 10:00 [Qemu-devel] Just to add one single point J. Mayer
2007-04-08 14:11 ` Thiemo Seufer
2007-04-08 16:03 ` J. Mayer [this message]
2007-04-08 23:19 ` Paul Brook
2007-04-09 1:22 ` Mike Frysinger
2007-04-09 10:06 ` J. Mayer
2007-04-09 21:26 ` Rob Landley
2007-04-09 22:32 ` J. Mayer
2007-04-11 21:49 ` Rob Landley
2007-04-12 7:56 ` Re:Qemu-PPC problems (was [Qemu-devel] Just to add one single point) J. Mayer
2007-04-12 15:49 ` Qemu-PPC " Jason Wessel
2007-04-12 16:34 ` Jason Wessel
2007-04-12 20:20 ` J. Mayer
2007-04-12 21:23 ` Jason Wessel
2007-04-14 21:28 ` Rob Landley
2007-04-18 21:34 ` Rob Landley
2007-04-14 19:50 ` Rob Landley
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=1176048185.1516.180.camel@rapid \
--to=l_indien@magic.fr \
--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 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.