public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Nick Andrew <nick@nick-andrew.net>
To: David Howells <dhowells@redhat.com>,
	David Woodhouse <David.Woodhouse@intel.com>,
	David Woodhouse <dwmw2@infradead.org>,
	James Morris <jmorris@namei.org>,
	Nick Andrew <nick@nick-andrew.net>,
	linux-mtd@lists.infradead.org
Cc: Nick Andrew <nick@nick-andrew.net>, linux-kernel@vger.kernel.org
Subject: [PATCH] Fix incorrect use of loose in fs.c
Date: Fri, 05 Dec 2008 14:08:06 +1100	[thread overview]
Message-ID: <20081205030806.32225.66382.stgit@marcab.local.tull.net> (raw)

Fix incorrect use of loose in fs.c

It should be 'lose', not 'loose'. Also fix a spelling error.

Signed-off-by: Nick Andrew <nick@nick-andrew.net>
---

 fs/jffs2/fs.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/fs/jffs2/fs.c b/fs/jffs2/fs.c
index 249305d..a598de9 100644
--- a/fs/jffs2/fs.c
+++ b/fs/jffs2/fs.c
@@ -386,7 +386,7 @@ int jffs2_remount_fs (struct super_block *sb, int *flags, char *data)
 	/* We stop if it was running, then restart if it needs to.
 	   This also catches the case where it was stopped and this
 	   is just a remount to restart it.
-	   Flush the writebuffer, if neccecary, else we loose it */
+	   Flush the writebuffer, if necessary, else we lose it */
 	if (!(sb->s_flags & MS_RDONLY)) {
 		jffs2_stop_garbage_collect_thread(c);
 		mutex_lock(&c->alloc_sem);

             reply	other threads:[~2008-12-05 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05  3:08 Nick Andrew [this message]
2008-12-05 10:47 ` [PATCH] Fix incorrect use of loose in fs.c David Howells

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=20081205030806.32225.66382.stgit@marcab.local.tull.net \
    --to=nick@nick-andrew.net \
    --cc=David.Woodhouse@intel.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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