From: Greg Ungerer <gerg@uclinux.org>
To: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH v2 0/3] m68k: fix ColdFire support
Date: Tue, 23 Jun 2015 10:37:55 +1000 [thread overview]
Message-ID: <5588AA63.2060103@uclinux.org> (raw)
In-Reply-To: <55883C92.9070505@suse.de>
Hi Andreas,
On 23/06/15 02:49, Andreas Färber wrote:
> Am 20.06.2015 um 06:55 schrieb Greg Ungerer:
>> I have one more fix still to come for the qemu mcf_fec.c net driver.
>> It currently doesn't support the mdio actions or any attached phy and
>> this will cause the linux fec driver to fail probing.
>
> I still have some mcf_* device conversions back from KVM Forum 2012
> lying around somewhere, waiting for further cleanups for submission...
Please dust of and send if you have the time. Would be
great to have more.
Regards
Greg
next prev parent reply other threads:[~2015-06-23 0:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 13:43 [Qemu-devel] [PATCH v2 0/3] m68k: fix ColdFire support gerg
2015-06-19 13:43 ` [Qemu-devel] [PATCH v2 1/3] m68k: implement more ColdFire 5208 interrupt controller functionality gerg
2015-06-19 13:43 ` [Qemu-devel] [PATCH v2 2/3] m68k: implement move to/from usp register instruction gerg
2015-06-19 19:28 ` Laurent Vivier
2015-06-19 13:43 ` [Qemu-devel] [PATCH v2 3/3] m68k: fix usp processing on interrupt entry and exception exit gerg
2015-06-19 19:35 ` Laurent Vivier
2015-06-21 23:11 ` Greg Ungerer
2015-06-19 19:39 ` [Qemu-devel] [PATCH v2 0/3] m68k: fix ColdFire support Laurent Vivier
2015-06-20 4:55 ` Greg Ungerer
2015-06-20 17:03 ` Laurent Vivier
2015-06-22 16:49 ` Andreas Färber
2015-06-23 0:37 ` Greg Ungerer [this message]
2015-06-20 17:24 ` Laurent Vivier
2015-06-22 15:34 ` Peter Maydell
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=5588AA63.2060103@uclinux.org \
--to=gerg@uclinux.org \
--cc=afaerber@suse.de \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--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).