mm/memory.c: clarify a confusing comment for vm_iomap_memory
authorWang Wenhu <wenhu.wang@vivo.com>
Thu, 2 Apr 2020 04:09:07 +0000 (21:09 -0700)
committerLinus Torvalds <torvalds@linux-foundation.org>
Thu, 2 Apr 2020 16:35:30 +0000 (09:35 -0700)
commitabd69b9e0010b730259244f9909cff7d8318880f
treed269f04f9743e8c55443b3c127173fec0d54e14d
parent86a76331d94c4cfa72fe1831dbe4b492f66fdb81
mm/memory.c: clarify a confusing comment for vm_iomap_memory

The param "start" actually referes to the physical memory start, which is
to be mapped into virtual area vma.  And it is the field vma->vm_start
which stands for the start of the area.

Most of the time, we do not read through whole implementation of a
function but only the definition and essential comments.  Accurate
comments are definitely the base stone.

Signed-off-by: Wang Wenhu <wenhu.wang@vivo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Link: http://lkml.kernel.org/r/20200318052206.105104-1-wenhu.wang@vivo.com
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
mm/memory.c