Re: [PATCH] Fix compile failure for OM 2.6.17 in debug/nanosleep-verbose-on-remote.patch

Florian Delizy <[email protected]> Fri, 23 Feb 2007 15:32:46 +0100
Newsgroups gmane.linux.cluster.openmosix.devel
Message-ID <[email protected]>
Hello,
> Index: kernel/2.6.17/debug/nanosleep-verbose-on-remote.patch
> ===================================================================
> --- kernel/2.6.17/debug/nanosleep-verbose-on-remote.patch	(revision 17)
> +++ kernel/2.6.17/debug/nanosleep-verbose-on-remote.patch	(working copy)
> @@ -1,16 +1,12 @@
> ----
> - kernel/hrtimer.c |    1 +
> - 1 file changed, 1 insertion(+)
> -
> -Index: linux/kernel/hrtimer.c
> +Index: linux-2.6.17/kernel/hrtimer.c
>  ===================================================================
> ---- linux.orig/kernel/hrtimer.c	2007-01-04 18:57:08.000000000 +0100
> -+++ linux/kernel/hrtimer.c	2007-01-04 18:58:48.000000000 +0100
> +--- linux-2.6.17.orig/kernel/hrtimer.c	2007-02-21 01:01:07.000000000 -0500
> ++++ linux-2.6.17/kernel/hrtimer.c	2007-02-21 01:01:37.000000000 -0500
>  @@ -780,6 +780,7 @@
>   	if (!timespec_valid(&tu))
>   		return -EINVAL;
>   
> -+	printk( KERN_DEBUG "nanosleep [%d] for %d s %d ns\n", current->pid, tu.tv_sec, tu.nsec);
> ++	printk( KERN_DEBUG "nanosleep [%d] for %ld s %ld ns\n", current->pid, tu.tv_sec, tu.tv_nsec);
>   	return hrtimer_nanosleep(&tu, rmtp, HRTIMER_REL, CLOCK_MONOTONIC);
>   }
>   
>
>   
Hum, I didn't see this warning ;) my mistake. But How does it make the 
build to "fail" ?


BTW, I'll check why the patches don't apply cleanly, but I can't do that 
soon,

Florian

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV