[PATCH] update kfree, vfree, and vunmap kerneldoc

This patch clarifies NULL handling of kfree() and vfree().  I addition,
wording of calling context restriction for vfree() and vunmap() are changed
from "may not" to "must not."

Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
Acked-by: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

1 files changed, 4 insertions, 3 deletions

diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 67b358e57ef6..13c3d82968ae 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -332,9 +332,10 @@ void __vunmap(void *addr, int deallocate_pages)
  *      @addr:          memory base address
  *
  *      Free the virtually contiguous memory area starting at @addr, as
- *      obtained from vmalloc(), vmalloc_32() or __vmalloc().
+ *      obtained from vmalloc(), vmalloc_32() or __vmalloc(). If @addr is
+ *      NULL, no operation is performed.
  *
- *      May not be called in interrupt context.
+ *      Must not be called in interrupt context.
  */
 void vfree(void *addr)
 {
@@ -352,7 +353,7 @@ EXPORT_SYMBOL(vfree);
  *      Free the virtually contiguous memory area starting at @addr,
  *      which was created from the page array passed to vmap().
  *
- *      May not be called in interrupt context.
+ *      Must not be called in interrupt context.
  */
 void vunmap(void *addr)
 {