linux-kernel - Re: [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53B566B7.9020505@redhat.com>
Date:	Thu, 03 Jul 2014 15:20:39 +0100
From:	Steven Whitehouse <swhiteho@...hat.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Jiri Kosina <trivial@...nel.org>
CC:	linux-kernel@...r.kernel.org, cluster-devel@...hat.com
Subject: Re: [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/

Hi,

Now in the -nmw tree. Thanks,

Steve.

On 29/06/14 11:21, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> Cc: Steven Whitehouse <swhiteho@...hat.com>
> Cc: cluster-devel@...hat.com
> ---
>   fs/gfs2/glops.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/gfs2/glops.c b/fs/gfs2/glops.c
> index fc1100781bbc..2ffc67dce87f 100644
> --- a/fs/gfs2/glops.c
> +++ b/fs/gfs2/glops.c
> @@ -234,8 +234,8 @@ static void inode_go_sync(struct gfs2_glock *gl)
>    * inode_go_inval - prepare a inode glock to be released
>    * @gl: the glock
>    * @flags:
> - *
> - * Normally we invlidate everything, but if we are moving into
> + *
> + * Normally we invalidate everything, but if we are moving into
>    * LM_ST_DEFERRED from LM_ST_SHARED or LM_ST_EXCLUSIVE then we
>    * can keep hold of the metadata, since it won't have changed.
>    *

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/