[PATCH] Immediate Values - PowerPC Optimization - kerneldoc for implementation

[Mathieu Desnoyers]

Immediate Values - PowerPC Optimization - kerneldoc for implementation

Add kerneldoc to Immediate Values (PowerPC Optimization) API.
It applies after
"Immediate Values - PowerPC Optimization - kerneldoc"

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxx>
CC: hch@xxxxxxxxxxxxx
---
 arch/powerpc/kernel/immediate.c |   15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

Index: linux-2.6-lttng/arch/powerpc/kernel/immediate.c
===================================================================
--- linux-2.6-lttng.orig/arch/powerpc/kernel/immediate.c	2007-07-15 19:10:32.000000000 -0400
+++ linux-2.6-lttng/arch/powerpc/kernel/immediate.c	2007-07-15 19:11:50.000000000 -0400
@@ -13,8 +13,11 @@
 
 #define LI_OPCODE_LEN	2
 
-/*
- * The immediate value are aligned.
+/**
+ * arch_immediate_update - update one immediate value
+ * @immediate: pointer of type const struct __immediate to update
+ *
+ * Update one immediate value. Must be called with immediate_mutex held.
  */
 int arch_immediate_update(const struct __immediate *immediate)
 {
@@ -68,8 +71,11 @@ int arch_immediate_update(const struct _
 	return 0;
 }
 
-/*
- * Very early initialization of the in-core immediate values.
+/**
+ * arch_immediate_update_early - update one immediate value at boot time
+ * @immediate: pointer of type const struct __immediate to update
+ *
+ * Update one immediate value at boot time.
  * We can use flush_icache_range, since the cpu identification has been done in
  * the early_init stage.
  */
@@ -95,4 +101,3 @@ void __init arch_immediate_update_early(
 	flush_icache_range((unsigned long)immediate->immediate,
 				immediate->size);
 }
-
-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/