linux-kernel - Re: [Cluster-devel] [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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 30 Jun 2014 11:30:16 -0400 (EDT)
From:	Bob Peterson <rpeterso@...hat.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Jiri Kosina <trivial@...nel.org>, cluster-devel@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [Cluster-devel] [PATCH -trivial 4/4] GFS2: memcontrol: Spelling
	s/invlidate/invalidate/

----- Original Message -----
> 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.
>   *
> --
> 1.9.1

Hi Geert,

ACK,

Steve is on holiday this week, but he will likely add it to the GFS2 nmw
git repo when he returns.

Regards,

Bob Peterson
Red Hat File Systems
--
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/