All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Peterson <rpeterso@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jiri Kosina <trivial@kernel.org>,
	cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [Cluster-devel] [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/
Date: Mon, 30 Jun 2014 11:30:16 -0400 (EDT)	[thread overview]
Message-ID: <1896340514.622143.1404142216566.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1404037299-31570-4-git-send-email-geert@linux-m68k.org>

----- Original Message -----
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Steven Whitehouse <swhiteho@redhat.com>
> Cc: cluster-devel@redhat.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

WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH -trivial 4/4] GFS2: memcontrol: Spelling	s/invlidate/invalidate/
Date: Mon, 30 Jun 2014 11:30:16 -0400 (EDT)	[thread overview]
Message-ID: <1896340514.622143.1404142216566.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1404037299-31570-4-git-send-email-geert@linux-m68k.org>

----- Original Message -----
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Cc: Steven Whitehouse <swhiteho@redhat.com>
> Cc: cluster-devel at redhat.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



  reply	other threads:[~2014-06-30 15:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 10:21 [PATCH -trivial 1/4] powerpc/simpleboot: Spelling s/trucate/truncate/ Geert Uytterhoeven
2014-06-29 10:21 ` Geert Uytterhoeven
2014-06-29 10:21 ` [PATCH -trivial 2/4] mtd: cmdlinepart: " Geert Uytterhoeven
2014-06-29 10:21   ` Geert Uytterhoeven
2014-07-03  0:26   ` Brian Norris
2014-07-03  0:26     ` Brian Norris
2014-06-29 10:21 ` [PATCH -trivial 3/4] mm: memcontrol: Spelling s/invlidate/invalidate/, s/trucate/truncate/ Geert Uytterhoeven
2014-06-29 10:21   ` Geert Uytterhoeven
2014-06-29 10:21 ` [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/ Geert Uytterhoeven
2014-06-29 10:21   ` [Cluster-devel] " Geert Uytterhoeven
2014-06-30 15:30   ` Bob Peterson [this message]
2014-06-30 15:30     ` Bob Peterson
2014-07-03 14:20   ` Steven Whitehouse
2014-07-03 14:20     ` [Cluster-devel] " Steven Whitehouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1896340514.622143.1404142216566.JavaMail.zimbra@redhat.com \
    --to=rpeterso@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.