2019-06-07 11:59:51

by Geert Uytterhoeven

Subject: [PATCH trivial] mm/vmalloc: Spelling s/configuraion/configuration/

Signed-off-by: Geert Uytterhoeven <[email protected]>
---
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

2019-06-07 23:13:29

by Souptick Joarder

Subject: Re: [PATCH trivial] mm/vmalloc: Spelling s/configuraion/configuration/

On Fri, Jun 7, 2019 at 5:05 PM Geert Uytterhoeven
<[email protected]> wrote:
>
> Signed-off-by: Geert Uytterhoeven <[email protected]>

Subject line should be s/informaion/information. With that fix,
Acked-by: Souptick Joarder <[email protected]>

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