[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160704201301.GA31238@vader>
Date: Mon, 4 Jul 2016 13:13:01 -0700
From: Omar Sandoval <osandov@...ndov.com>
To: Luis de Bethencourt <luisbg@....samsung.com>
Cc: linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] vfs: fix typo in link_path_walk()
On Mon, Jul 04, 2016 at 05:48:53PM +0100, Luis de Bethencourt wrote:
> Comment documenting the path parsing in link_path_walk() has a typo, fixing
> it.
>
> Signed-off-by: Luis de Bethencourt <luisbg@....samsung.com>
> ---
>
> Hello,
>
> Noticed this typo while studying the code paths when sys_open is called.
>
> Thanks,
> Luis
>
> fs/namei.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/namei.c b/fs/namei.c
> index 32f9fe9..ade7667 100644
> --- a/fs/namei.c
> +++ b/fs/namei.c
> @@ -2064,7 +2064,7 @@ static int link_path_walk(const char *name, struct nameidata *nd)
> if (!*name)
> goto OK;
> /*
> - * If it wasn't NUL, we know it was '/'. Skip that
> + * If it wasn't NULL, we know it was '/'. Skip that
> * slash, and continue until no more slashes.
> */
> do {
> --
> 2.6.4
NUL is the ASCII '\0' character. NULL is a pointer. So NUL is correct.
--
Omar
Powered by blists - more mailing lists