[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200717185624.2009393-11-dwlsalmeida@gmail.com>
Date: Fri, 17 Jul 2020 15:56:10 -0300
From: "Daniel W. S. Almeida" <dwlsalmeida@...il.com>
To: corbet@....net, mchehab@...nel.org
Cc: "Daniel W. S. Almeida" <dwlsalmeida@...il.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 11/25] Documentation: vmalloc.c: fix sphinx warning
From: "Daniel W. S. Almeida" <dwlsalmeida@...il.com>
Fix the following warning:
warning: Excess function parameter 'prot' description in
'vm_map_ram'
Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@...il.com>
---
mm/vmalloc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 3091c2ca60dfd..957a0be772702 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -1862,7 +1862,6 @@ EXPORT_SYMBOL(vm_unmap_ram);
* @pages: an array of pointers to the pages to be mapped
* @count: number of pages
* @node: prefer to allocate data structures on this node
- * @prot: memory protection to use. PAGE_KERNEL for regular RAM
*
* If you use this function for less than VMAP_MAX_ALLOC pages, it could be
* faster than vmap so it's good. But if you mix long-life and short-life
--
2.27.0
Powered by blists - more mailing lists