From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Port E9 hack
Date: Sun, 06 Feb 2005 14:44:56 +0100 [thread overview]
Message-ID: <42061F58.3080001@bellard.org> (raw)
In-Reply-To: <420613B7.2070202@enix.org>
> I had no feedback regarding my port E9 hack patch. Does that mean that
> this functionnality is not desirable for Qemu ? Should I give up with
> this ?
Don't worry, it will be merged someday. Just a question : why did you
code it as if there were several port E9 devices ?
Fabrice.
next prev parent reply other threads:[~2005-02-06 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 12:55 [Qemu-devel] Port E9 hack Thomas Petazzoni
2005-02-06 13:33 ` Magnus Damm
2005-02-06 13:44 ` Fabrice Bellard [this message]
2005-02-06 14:30 ` Thomas Petazzoni
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=42061F58.3080001@bellard.org \
--to=fabrice@bellard.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).