linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>,
	MTD Maling List <linux-mtd@lists.infradead.org>
Cc: Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 1/4] jffs2: remove lock_super
Date: Mon,  7 May 2012 19:56:50 +0300	[thread overview]
Message-ID: <1336409813-6365-2-git-send-email-dedekind1@gmail.com> (raw)
In-Reply-To: <1336409813-6365-1-git-send-email-dedekind1@gmail.com>

From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>

We do not need 'lock_super()'/'unlock_super()' in JFFS2 - kill them.

Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
---
 fs/jffs2/super.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/fs/jffs2/super.c b/fs/jffs2/super.c
index f9916f3..3422a2d 100644
--- a/fs/jffs2/super.c
+++ b/fs/jffs2/super.c
@@ -67,15 +67,12 @@ static void jffs2_write_super(struct super_block *sb)
 {
 	struct jffs2_sb_info *c = JFFS2_SB_INFO(sb);
 
-	lock_super(sb);
 	sb->s_dirt = 0;
 
 	if (!(sb->s_flags & MS_RDONLY)) {
 		jffs2_dbg(1, "%s()\n", __func__);
 		jffs2_flush_wbuf_gc(c, 0);
 	}
-
-	unlock_super(sb);
 }
 
 static const char *jffs2_compr_name(unsigned int compr)
-- 
1.7.7.6

  reply	other threads:[~2012-05-07 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 16:56 [PATCH v2 0/4] do not use s_dirt in JFFS2 Artem Bityutskiy
2012-05-07 16:56 ` Artem Bityutskiy [this message]
2012-05-07 16:56 ` [PATCH v2 2/4] jffs2: remove unnecessary GC pass on umount Artem Bityutskiy
2012-05-07 16:56 ` [PATCH v2 3/4] jffs2: remove unnecessary GC pass on sync Artem Bityutskiy
2012-05-07 16:56 ` [PATCH v2 4/4] jffs2: get rid of jffs2_sync_super Artem Bityutskiy

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=1336409813-6365-2-git-send-email-dedekind1@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.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;
as well as URLs for NNTP newsgroup(s).