From: Jeff Dike <jdike@addtoit.com>
To: Ram Pai <linuxram@us.ibm.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [RFC PATCH] fixes for some compilation errors
Date: Tue, 15 Nov 2005 20:23:09 -0500 [thread overview]
Message-ID: <20051116012309.GB11520@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20051115233006.GA31279@RAM>
On Tue, Nov 15, 2005 at 03:30:06PM -0800, Ram Pai wrote:
> -extern void *switch_to_tt(void *prev, void *next);
> +extern void switch_to_tt(void *prev, void *next);
Oops, I hadn't built with CONFIG_MODE_TT enabled in a while.
> -#include <asm/signal.h>
> +//#include <asm/signal.h>
I now have this as <signal.h> which works here - can you check this?
> +#include "kern_constants.h"
I already have this, I may not have refreshed the patch before pushing it
out.
> err = stub_syscall3(__NR_setitimer, ITIMER_VIRTUAL,
> - (long) STUB_DATA(timer), 0);
> + (long) &from->timer, 0);
What were these doing to you?
I pushed out a fixed patchset - can you recheck?
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-11-16 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 23:30 [uml-devel] [RFC PATCH] fixes for some compilation errors Ram Pai
2005-11-16 1:23 ` Jeff Dike [this message]
2005-11-16 10:42 ` Ram Pai
2005-11-16 19:18 ` Jeff Dike
2005-11-17 22:43 ` Ram Pai
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=20051116012309.GB11520@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linuxram@us.ibm.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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