Piteball/android_kernel_samsung_msm8976
1
1
Fork 0
mirror of https://github.com/team-infusion-developers/android_kernel_samsung_msm8976.git synced 2024-11-01 02:21:16 +00:00
Code Issues Projects Releases Wiki Activity

vmalloc: remove KM_USER0 from comments

Browse source 
Signed-off-by: Cong Wang <amwang@redhat.com>
This commit is contained in:
Cong Wang 2012-06-23 11:30:16 +08:00
parent 167885e593
commit a8e5202d09
1 changed files with 2 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
mm/vmalloc.c
View file

@ -1975,9 +1975,7 @@ static int aligned_vwrite(char *buf, char *addr, unsigned long count)
* IOREMAP area is treated as memory hole and no copy is done. * IOREMAP area is treated as memory hole and no copy is done.
* *
* If [addr...addr+count) doesn't includes any intersects with alive * If [addr...addr+count) doesn't includes any intersects with alive
* vm_struct area, returns 0. * vm_struct area, returns 0. @buf should be kernel's buffer.
* @buf should be kernel's buffer. Because this function uses KM_USER0,
* the caller should guarantee KM_USER0 is not used.
* *
* Note: In usual ops, vread() is never necessary because the caller * Note: In usual ops, vread() is never necessary because the caller
* should know vmalloc() area is valid and can use memcpy(). * should know vmalloc() area is valid and can use memcpy().
@ -2051,9 +2049,7 @@ finished:
* IOREMAP area is treated as memory hole and no copy is done. * IOREMAP area is treated as memory hole and no copy is done.
* *
* If [addr...addr+count) doesn't includes any intersects with alive * If [addr...addr+count) doesn't includes any intersects with alive
* vm_struct area, returns 0. * vm_struct area, returns 0. @buf should be kernel's buffer.
* @buf should be kernel's buffer. Because this function uses KM_USER0,
* the caller should guarantee KM_USER0 is not used.
* *
* Note: In usual ops, vwrite() is never necessary because the caller * Note: In usual ops, vwrite() is never necessary because the caller
* should know vmalloc() area is valid and can use memcpy(). * should know vmalloc() area is valid and can use memcpy().