From: Mark McLoughlin <markmc@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-sh4 broken
Date: Mon, 12 Jan 2009 11:13:12 +0000 [thread overview]
Message-ID: <1231758792.4290.130.camel@localhost.localdomain> (raw)
In-Reply-To: <496A4162.7020908@mail.berlios.de>
On Sun, 2009-01-11 at 19:58 +0100, Stefan Weil wrote:
> Jean-Christophe PLAGNIOL-VILLARD schrieb:
> > Hi,
> >
> > The following commit r6216 or afdadbe3 (git)
> > Add a model string to VLANClientState (Mark McLoughlin)
> > brake the qemu system SH4 emulation
> >
> > Mark could you take a look
> >
> > Best Regards,
> > J.
> This might be fixed with the patch I just sent to the list
> ([Qemu-devel] [BUG][PATCH] Fix a nullpointer crash caused by r6216).
>
> Could you please try it?
Hmm, I thought Anthony had already merged my fixes for this stuff ...
but it seems not.
See the four patches starting with:
[PATCH 1/4] Add qemu_check_nic_model() and qemu_check_nic_model_list()
http://lists.gnu.org/archive/html/qemu-devel/2009-01/msg00296.html
Cheers,
Mark.
prev parent reply other threads:[~2009-01-12 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 14:23 [Qemu-devel] qemu-sh4 broken Jean-Christophe PLAGNIOL-VILLARD
2009-01-11 18:58 ` Stefan Weil
2009-01-12 11:13 ` Mark McLoughlin [this message]
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=1231758792.4290.130.camel@localhost.localdomain \
--to=markmc@redhat.com \
--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).