Messages in this thread Patch in this message | | | From | Geert Uytterhoeven <> | Subject | [PATCH trivial] mm/vmalloc: Spelling s/configuraion/configuration/ | Date | Fri, 7 Jun 2019 13:35:09 +0200 |
| |
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- mm/vmalloc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 7350a124524bb4b2..08b8b5a117576561 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -2783,7 +2783,7 @@ static int aligned_vwrite(char *buf, char *addr, unsigned long count) * Note: In usual ops, vread() is never necessary because the caller * should know vmalloc() area is valid and can use memcpy(). * This is for routines which have to access vmalloc area without - * any informaion, as /dev/kmem. + * any information, as /dev/kmem. * * Return: number of bytes for which addr and buf should be increased * (same number as @count) or %0 if [addr...addr+count) doesn't @@ -2862,7 +2862,7 @@ long vread(char *buf, char *addr, unsigned long count) * Note: In usual ops, vwrite() is never necessary because the caller * should know vmalloc() area is valid and can use memcpy(). * This is for routines which have to access vmalloc area without - * any informaion, as /dev/kmem. + * any information, as /dev/kmem. * * Return: number of bytes for which addr and buf should be * increased (same number as @count) or %0 if [addr...addr+count) -- 2.17.1
| |