From: "Ben Taylor" <bentaylor.solx86@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu+linux-kernel-2.6.25
Date: Mon, 12 May 2008 10:00:03 -0400 [thread overview]
Message-ID: <cef699d70805120700g3f21c9dr665ec09420b4e268@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.61.0805120953470.873@cps203.cps.cmich.edu>
On Mon, May 12, 2008 at 9:56 AM, ISHWAR RATTAN <rattan@cps.cmich.edu> wrote:
>
> kqemu-1.3.0pre11 does not compile under Linx
> kernel-2.6.25. Is this known issue or is there
> a work around?
Try the code in
http://svn9.cvsdude.com/kdesolaris/kqemu/trunk/1.0.3pre11/kqemu
Ben
next prev parent reply other threads:[~2008-05-12 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 13:56 [Qemu-devel] kqemu+linux-kernel-2.6.25 ISHWAR RATTAN
2008-05-12 14:00 ` Ben Taylor [this message]
2008-05-12 14:37 ` ISHWAR RATTAN
2008-05-12 14:44 ` Laurence Hellyer
2008-05-12 15:12 ` ISHWAR RATTAN
2008-05-12 15:53 ` Ben Taylor
2008-05-12 18:44 ` ISHWAR RATTAN
2008-05-13 14:11 ` ISHWAR RATTAN
2008-05-13 15:49 ` Ben Taylor
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=cef699d70805120700g3f21c9dr665ec09420b4e268@mail.gmail.com \
--to=bentaylor.solx86@gmail.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).