From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jiri Kosina <trivial@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Steven Whitehouse <swhiteho@redhat.com>,
cluster-devel@redhat.com
Subject: [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/
Date: Sun, 29 Jun 2014 12:21:39 +0200 [thread overview]
Message-ID: <1404037299-31570-4-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1404037299-31570-1-git-send-email-geert@linux-m68k.org>
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
next prev parent reply other threads:[~2014-06-29 10:21 UTC|newest]
Thread overview: 7+ 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 ` [PATCH -trivial 2/4] mtd: cmdlinepart: " Geert Uytterhoeven
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 [this message]
2014-06-30 15:30 ` [Cluster-devel] [PATCH -trivial 4/4] GFS2: memcontrol: Spelling s/invlidate/invalidate/ Bob Peterson
2014-07-03 14:20 ` 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=1404037299-31570-4-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®