[2.6 patch] mm/nommu.c: try to fix __vmalloc

Linus changed the second argument of __vmalloc from int to unsigned int 
breaking the compilation for CONFIG_MMU=n configurations (since he only 
changed vmalloc.c but not nommu.c).

Is this patch the correct fix, or do I oversee an underlying problem?

Signed-off-by: Adrian Bunk <[email protected]>

--- linux-2.6.12-rc4-mm1/mm/nommu.c.old	2005-05-13 06:51:33.000000000 +0200
+++ linux-2.6.12-rc4-mm1/mm/nommu.c	2005-05-13 06:55:33.000000000 +0200
@@ -146,7 +146,7 @@
 	kfree(addr);
 }
 
-void *__vmalloc(unsigned long size, int gfp_mask, pgprot_t prot)
+void *__vmalloc(unsigned long size, unsigned int __nocast gfp_mask, pgprot_t prot)
 {
 	/*
 	 * kmalloc doesn't like __GFP_HIGHMEM for some reason

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Prev by Date: Re: Need kernel patch to compile with Intel compiler
• Next by Date: [ANNOUNCE] mtkdiff 20050513
• Previous by thread: SCTP: use lib/libcrc32c.c instead of net/sctp/crc32c.c?
• Next by thread: [ANNOUNCE] mtkdiff 20050513
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]