From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: "David S. Miller" <davem@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Alpha update
Date: 01 May 2003 21:27:04 +0200 [thread overview]
Message-ID: <871xzicvsn.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <20030430.070101.83594504.davem@redhat.com>
"David S. Miller" <davem@redhat.com> writes:
> For what it's worth, after some debugging I have sparc successfully
> running the test/hello program using the mmap4k code as well.
Cool. Did you have change anything? How about dynamically linked
binaries, do they work?
--
Falk
next prev parent reply other threads:[~2003-05-01 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 11:34 [Qemu-devel] Alpha update Falk Hueffner
2003-04-30 10:48 ` David S. Miller
2003-04-30 14:01 ` David S. Miller
2003-05-01 19:27 ` Falk Hueffner [this message]
2003-05-01 18:48 ` David S. Miller
2003-05-03 17:29 ` fabrice.bellard
2003-05-03 16:32 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-05-11 1:41 Falk Hueffner
2003-05-11 13:10 ` Fabrice Bellard
2003-05-11 18:40 ` David S. Miller
2003-05-11 22:27 ` Fabrice Bellard
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=871xzicvsn.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.de \
--cc=davem@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).