[PATCH][TRIVIAL] Fix comments in mm/memblock.c

From: Li Zhong
Date: Wed Jun 13 2012 - 23:48:27 EST


Make the parameter names in comments consistent with the actual ones
used in the function.

Signed-off-by: Li Zhong <zhong@xxxxxxxxxxxxxxxxxx>
---
mm/memblock.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/mm/memblock.c b/mm/memblock.c
index 952123e..76cb09f 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -540,9 +540,9 @@ int __init_memblock memblock_reserve(phys_addr_t
base, phys_addr_t size)
* __next_free_mem_range - next function for for_each_free_mem_range()
* @idx: pointer to u64 loop variable
* @nid: nid: node selector, %MAX_NUMNODES for all nodes
- * @p_start: ptr to phys_addr_t for start address of the range, can be
%NULL
- * @p_end: ptr to phys_addr_t for end address of the range, can be %
NULL
- * @p_nid: ptr to int for nid of the range, can be %NULL
+ * @out_start: ptr to phys_addr_t for start address of the range, can
be %NULL
+ * @out_end: ptr to phys_addr_t for end address of the range, can be %
NULL
+ * @out_nid: ptr to int for nid of the range, can be %NULL
*
* Find the first free area from *@idx which matches @nid, fill the out
* parameters, and update *@idx for the next iteration. The lower
32bit of
--
1.7.9.5

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