[RFC][PATCH] inline a few tiny functions in init/initramfs.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A few functions in init/initramfs.c are so simple that I don't see why *any* 
point in them having to bear the cost of a function call.
Wouldn't something like the patch below make sense ?


Signed-off-by: Jesper Juhl <[email protected]>
---

 init/initramfs.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

--- linux-2.6.14-rc2-git3-orig/init/initramfs.c	2005-09-22 00:28:39.000000000 +0200
+++ linux-2.6.14-rc2-git3/init/initramfs.c	2005-09-24 01:21:55.000000000 +0200
@@ -14,12 +14,12 @@ static void __init error(char *x)
 		message = x;
 }
 
-static void __init *malloc(size_t size)
+static inline void __init *malloc(size_t size)
 {
 	return kmalloc(size, GFP_KERNEL);
 }
 
-static void __init free(void *where)
+static inline void __init free(void *where)
 {
 	kfree(where);
 }
@@ -155,7 +155,7 @@ static void __init read_into(char *buf, 
 
 static __initdata char *header_buf, *symlink_buf, *name_buf;
 
-static int __init do_start(void)
+static inline int __init do_start(void)
 {
 	read_into(header_buf, 110, GotHeader);
 	return 0;


-
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/

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