public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Peter Grayson <pgrayson@realmsys.com>
To: linux-mtd@lists.infradead.org
Subject: [PATCH] More removing virtual blocks
Date: Wed, 31 Aug 2005 23:18:22 -0600	[thread overview]
Message-ID: <1125551902.7076.22.camel@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 125 bytes --]

Here is a follow-on patch for Ferenc's patch that removes virtual block
support from jffs2. Just a couple loose ends.

Pete


[-- Attachment #2: jffs2-novirtblock2.patch --]
[-- Type: text/x-patch, Size: 1008 bytes --]

[JFFS2] Follow-on to Ferenc's jffs2-novirtblocks patch
[From: Peter Grayson <pgrayson@realmsys.com>]
diff -Narup mtd/fs/jffs2/fs.c mtd-novirtblock2/fs/jffs2/fs.c
--- mtd/fs/jffs2/fs.c	2005-08-31 17:56:25.000000000 -0600
+++ mtd-novirtblock2/fs/jffs2/fs.c	2005-08-31 23:07:31.887566728 -0600
@@ -469,10 +469,6 @@ int jffs2_do_fill_super(struct super_blo
 			c->flash_size / 1024);
 	}
 
-	if (c->sector_size != c->mtd->erasesize)
-		printk(KERN_INFO "jffs2: Erase block size too small (%dKiB). Using virtual blocks size (%dKiB) instead\n", 
-			c->mtd->erasesize / 1024, c->sector_size / 1024);
-
 	if (c->flash_size < 5*c->sector_size) {
 		printk(KERN_ERR "jffs2: Too few erase blocks (%d)\n", c->flash_size / c->sector_size);
 		return -EINVAL;
@@ -522,7 +518,7 @@ int jffs2_do_fill_super(struct super_blo
 	iput(root_i);
 	jffs2_free_ino_caches(c);
 	jffs2_free_raw_node_refs(c);
-	if (c->mtd->flags & MTD_NO_VIRTBLOCKS)
+	if (jffs2_blocks_use_vmalloc(c))
 		vfree(c->blocks);
 	else
 		kfree(c->blocks);

             reply	other threads:[~2005-09-01  5:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01  5:18 Peter Grayson [this message]
2005-09-01  8:44 ` [PATCH] More removing virtual blocks Ferenc Havasi

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=1125551902.7076.22.camel@localhost.localdomain \
    --to=pgrayson@realmsys.com \
    --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